CEPH filesystem development
 help / color / mirror / Atom feed
From: "Max A. Krasilnikov" <pseudo-z2DuZ08HpnDk1uMJSBkQmQ@public.gmane.org>
Cc: ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ceph-users <ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org>
Subject: Re: un-even data filled on OSDs
Date: Fri, 10 Jun 2016 13:29:24 +0300	[thread overview]
Message-ID: <20160610102924.GE35337@colocall.net> (raw)
In-Reply-To: <CANA9Uk4Bddii2vBgExF3tM9hs2CByefep8mpUZpHKFCyzEFyXg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hello! 

On Fri, Jun 10, 2016 at 07:38:10AM +0530, swamireddy wrote:

> Blair - Thanks for the details. I used to set the low priority for
> recovery during the rebalance/recovery activity.
> Even though I set the recovery_priority as 5 (instead of 1) and
> client-op_priority set as 63, some of my customers complained that
> their VMs are not reachable for a few mins/secs during the reblancing
> task. Not sure, these low priority configurations are doing the job as
> its.

It is true up to Hammer at least. I have no possibility to test it on jevel
setup due to my company policy (part of my cluster already is jevel, but I can
not continue upgrade due to direct directive).

> Thanks
> Swami

-- 
WBR, Max A. Krasilnikov

      parent reply	other threads:[~2016-06-10 10:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  7:32 un-even data filled on OSDs M Ranga Swami Reddy
     [not found] ` <CANA9Uk4NH7H4kQjEzeNp26bvar5DRWvnNdPff-wCJDRfb1be_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-07 12:30   ` Sage Weil
2016-06-07 12:40     ` M Ranga Swami Reddy
     [not found]       ` <CANA9Uk6YXFpAyp+jUgq7Cc9nRwR4Ha=UO-0nPrEAxy8A_GxGNA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-07 13:07         ` Sage Weil
2016-06-07 13:11           ` M Ranga Swami Reddy
2016-06-07 13:21             ` Sage Weil
     [not found]               ` <alpine.DEB.2.11.1606070921430.6221-Wo5lQnKln9t9PHm/lf2LFUEOCMrvLtNR@public.gmane.org>
2016-06-07 13:52                 ` Corentin Bonneton
     [not found]                   ` <1F4849EF-DC23-468C-9008-7F1CCEE50F36-Ir4F46R2WEs@public.gmane.org>
2016-06-07 16:45                     ` M Ranga Swami Reddy
2016-06-07 15:11                 ` Markus Blank-Burian
2016-06-08  1:05             ` Blair Bethwaite
2016-06-08  5:04               ` M Ranga Swami Reddy
2016-06-08  5:08                 ` Blair Bethwaite
     [not found]                   ` <CA+z5DsxrovFX6GGmcfWAhNm69fb3s4-M6wMSR1u5vzdV8LTSSg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-08  5:09                     ` M Ranga Swami Reddy
2016-06-09 10:20                 ` M Ranga Swami Reddy
     [not found]                   ` <CANA9Uk48oQ7sjd614LzYy=7HxYfmO8qZxoQCC62wYeOdsBPFeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-09 12:20                     ` Blair Bethwaite
2016-06-10  2:08                       ` M Ranga Swami Reddy
2016-06-10  2:10                         ` Blair Bethwaite
2016-06-10  8:18                           ` M Ranga Swami Reddy
     [not found]                         ` <CANA9Uk4Bddii2vBgExF3tM9hs2CByefep8mpUZpHKFCyzEFyXg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-10 10:29                           ` Max A. Krasilnikov [this message]

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=20160610102924.GE35337@colocall.net \
    --to=pseudo-z2duz08hpndk1umjsbkqmq@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@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