From: Abhishek Lekshmanan <abhishek-IBi9RG/b67k@public.gmane.org>
To: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ceph-users-Qp0mS5GaXlQ@public.gmane.org,
ceph-maintainers-Qp0mS5GaXlQ@public.gmane.org,
ceph-announce-Qp0mS5GaXlQ@public.gmane.org
Subject: Luminous v12.2.10 released
Date: Tue, 27 Nov 2018 15:50:16 +0100 [thread overview]
Message-ID: <87y39e4lsn.fsf@suse.com> (raw)
We're happy to announce the tenth bug fix release of the Luminous
v12.2.x long term stable release series. The previous release, v12.2.9,
introduced the PG hard-limit patches which were found to cause an issue
in certain upgrade scenarios, and this release was expedited to revert
those patches. If you already successfully upgraded to v12.2.9, you
should **not** upgrade to v12.2.10, but rather **wait** for a release in
which http://tracker.ceph.com/issues/36686 is addressed. All other users
are encouraged to upgrade to this release.
Notable Changes
---------------
* This release reverts the PG hard-limit patches added in v12.2.9 in which,
a partial upgrade during a recovery/backfill, can cause the osds on the
previous version, to fail with assert(trim_to <= info.last_complete). The
workaround for users is to upgrade and restart all OSDs to a version with the
pg hard limit, or only upgrade when all PGs are active+clean.
See also: http://tracker.ceph.com/issues/36686
As mentioned above if you've successfully upgraded to v12.2.9 DO NOT
upgrade to v12.2.10 until the linked tracker issue has been fixed.
* The bluestore_cache_* options are no longer needed. They are replaced
by osd_memory_target, defaulting to 4GB. BlueStore will expand
and contract its cache to attempt to stay within this
limit. Users upgrading should note this is a higher default
than the previous bluestore_cache_size of 1GB, so OSDs using
BlueStore will use more memory by default.
For more details, see BlueStore docs[1]
For the complete release notes with changelog, please check out the
release blog entry at:
http://ceph.com/releases/v12-2-10-luminous-released
Getting ceph:
------------
* Git at git://github.com/ceph/ceph.git
* Tarball at http://download.ceph.com/tarballs/ceph-12.2.10.tar.gz
* For packages, see http://docs.ceph.com/docs/master/install/get-packages/
* Release git sha1: 177915764b752804194937482a39e95e0ca3de94
[1]: http://docs.ceph.com/docs/master/rados/configuration/bluestore-config-ref/#cache-size
--
Abhishek Lekshmanan
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
_______________________________________________
Ceph-announce mailing list
Ceph-announce@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-announce-ceph.com
next reply other threads:[~2018-11-27 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 14:50 Abhishek Lekshmanan [this message]
[not found] ` <87y39e4lsn.fsf-IBi9RG/b67k@public.gmane.org>
2018-12-12 16:03 ` Luminous v12.2.10 released Dan van der Ster
[not found] ` <CABZ+qqmTR9iE==GXGK1mxj_CCBQKSBtkL3WChv4UGQ_zHNo0pA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-12 17:35 ` David Galloway
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y39e4lsn.fsf@suse.com \
--to=abhishek-ibi9rg/b67k@public.gmane.org \
--cc=ceph-announce-Qp0mS5GaXlQ@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-maintainers-Qp0mS5GaXlQ@public.gmane.org \
--cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox