All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@42on.com>
To: zou wonder <wonder.zou@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: What the ceph do when detecting one OSD overloaded?
Date: Fri, 06 Jun 2014 12:35:12 +0200	[thread overview]
Message-ID: <53919960.3010903@42on.com> (raw)
In-Reply-To: <CAOXjUBxO69M0dKU0kSx0i8Zp8pNR_XEhNWTsipRK2YC3L9NKTw@mail.gmail.com>

On 06/06/2014 11:27 AM, zou wonder wrote:
> Hi Wido:
>
>     Thanks for your kindness, i checked the codes just now, seems there
> were no overload related thing in CRUSH codes. It is a little bit not
> consistent with the CRUSH paper.
>   So if the %100 utilized OSD is returned, the objects will still be
> written on the underlined storage device?
>

Yes. If the OSD is up/in it will be selected by CRUSH and data will be 
read from it and written to it.

Again, having one OSD being 100% utilized and the rest 40% is not 
something you'll see very often since you stripe data over objects.

> How about the device failure case? All the objects on the failure
> device will be replicated to the good ones? once the device is
> recoverd, the data will be replicated back?

When the OSD fails recovery will kick in after 5 minutes and the data 
will find a new location.

If the OSD comes back, the data goes back to that OSD.

>
> Best Regards
> Zou
>
> On Fri, Jun 6, 2014 at 4:27 PM, Wido den Hollander <wido@42on.com> wrote:
>> On 06/06/2014 10:14 AM, zou wonder wrote:
>>>
>>> Hi buddies,
>>>
>>>     I am doing investigation on Ceph and Swift,and I am newbie to Ceph.
>>>
>>> I am unclear to the behaviour of the Ceph when there is overload
>>> situation.
>>> According to the doc, when Ceph do CRUSH, if it find the OSD is overload,
>>> it will skip it to select the other OSD. It means if the OSD don't get
>>> overloaded
>>> the object should be put in this OSD. So how about the original on put on
>>> this OSD when it is not get overloaded?
>>> Can we read it ? When doing CRUSH , the OSD will be skip.
>>>
>>
>> CRUSH will not take any performance characteristics into account. If a OSD
>> is 100% utilized it will still be selected by CRUSH.
>>
>> Keep in mind however that Block Devices are striped in 4MB chunks and the
>> same happens for Objects stored via the RADOS Gateway.
>>
>>> If my understanding is wrong, please correct me.
>>>
>>> Best Regards,
>>> zou
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>
>>
>> --
>> Wido den Hollander
>> 42on B.V.
>> Ceph trainer and consultant
>>
>> Phone: +31 (0)20 700 9902
>> Skype: contact42on


-- 
Wido den Hollander
42on B.V.
Ceph trainer and consultant

Phone: +31 (0)20 700 9902
Skype: contact42on

  reply	other threads:[~2014-06-06 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  8:14 What the ceph do when detecting one OSD overloaded? zou wonder
2014-06-06  8:27 ` Wido den Hollander
2014-06-06  9:27   ` zou wonder
2014-06-06 10:35     ` Wido den Hollander [this message]
2014-06-06 15:46     ` Sage Weil

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=53919960.3010903@42on.com \
    --to=wido@42on.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=wonder.zou@gmail.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.