From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sweil@redhat.com>, Mike Dawson <mike.dawson@cloudapt.com>
Cc: ceph-devel@vger.kernel.org, ceph-users@ceph.com,
ceph-maintainers@ceph.com
Subject: Re: [Ceph-maintainers] v0.67.11 dumpling released
Date: Thu, 25 Sep 2014 17:59:01 +0200 [thread overview]
Message-ID: <54243BC5.9030803@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1409250852020.16795@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 2305 bytes --]
Hi,
On 25/09/2014 17:53, Sage Weil wrote:
> On Thu, 25 Sep 2014, Mike Dawson wrote:
>> On 9/25/2014 11:09 AM, Sage Weil wrote:
>>> v0.67.11 "Dumpling"
>>> ===================
>>>
>>> This stable update for Dumpling fixes several important bugs that affect a
>>> small set of users.
>>>
>>> We recommend that all Dumpling users upgrade at their convenience. If
>>> none of these issues are affecting your deployment there is no urgency.
>>>
>>>
>>> Notable Changes
>>> ---------------
>>>
>>> * common: fix sending dup cluster log items (#9080 Sage Weil)
>>> * doc: several doc updates (Alfredo Deza)
>>> * libcephfs-java: fix build against older JNI headesr (Greg Farnum)
>>> * librados: fix crash in op timeout path (#9362 Matthias Kiefer, Sage Weil)
>>> * librbd: fix crash using clone of flattened image (#8845 Josh Durgin)
>>> * librbd: fix error path cleanup when failing to open image (#8912 Josh
>>> Durgin)
>>> * mon: fix crash when adjusting pg_num before any OSDs are added (#9052
>>> Sage Weil)
>>> * mon: reduce log noise from paxos (Aanchal Agrawal, Sage Weil)
>>> * osd: allow scrub and snap trim thread pool IO priority to be adjusted
>>> (Sage Weil)
>>
>> Sage,
>>
>> Thanks for the great work! Could you provide any links describing how to tune
>> the scrub and snap trim thread pool IO priority? I couldn't find these
>> settings in the docs.
>
> It's
>
> osd disk thread ioprio class = idle
> osd disk thread ioprio priority = 0
>
> Note that this is a short-term solution; we eventaully want to send all IO
> through the same queue so that we can prioritize things more carefully.
> This setting will most likely go away in the future.
>
The documentation for these can be found at
http://ceph.com/docs/giant/rados/configuration/osd-config-ref/#operations
Control-f ioprio
Cheers
>> IIUC, 0.67.11 does not include the proposed changes to address #9487 or
>> #9503, right?
>
> Correct. That will come later once it's gone through more testing.
>
> Thanks!
> sage
> _______________________________________________
> Ceph-maintainers mailing list
> Ceph-maintainers@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-maintainers-ceph.com
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-09-25 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 15:09 v0.67.11 dumpling released Sage Weil
2014-09-25 15:47 ` Mike Dawson
[not found] ` <5424390D.6010203-ffsCFlcjuZBWk0Htik3J/w@public.gmane.org>
2014-09-25 15:53 ` Sage Weil
2014-09-25 15:59 ` Loic Dachary [this message]
2014-09-25 15:55 ` Dan Van Der Ster
[not found] ` <70392B2C-5476-4221-86A0-307180085655-vJEk5272eHo@public.gmane.org>
2014-09-25 16:00 ` Sage Weil
2014-09-25 17:27 ` Mike Dawson
2014-09-25 17:41 ` Alfredo Deza
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=54243BC5.9030803@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-maintainers@ceph.com \
--cc=ceph-users@ceph.com \
--cc=mike.dawson@cloudapt.com \
--cc=sweil@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.