From: "Łukasz Chrustek" <skidoo@tlen.pl>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: problem with removing osd
Date: Thu, 29 Dec 2016 23:02:11 +0100 [thread overview]
Message-ID: <10710520745.20161229230211@tlen.pl> (raw)
In-Reply-To: <alpine.DEB.2.11.1612292137550.10615@piezo.novalocal>
Hi,
Thank You very much for analize and the file ! I had similar :) but
wasn't sure if it wan't distroy something in cluster.
> The encoded tree bucket -11 had bad values. I don't really trust the tree
> bucket code in crush... it's not well tested (and is a poor balance
> computation and efficiency anyway). We should probably try to remove tree
> entirely.
> I've attached a fixed map that you can inject with
> ceph osd setcrushmap -i <filename>
Now it works, and also ceph osd crush dump -f json-pretty runs OK.
> Bucket -11 is now empty; not sure what was supposed to be in it.
this server will be reinstalled, there where three osds.
> I suggest switching all of your tree buckets over to straw2 as soon as
> possible. Note that this will result in some rebalancing. You could do
> it one bucket a time if that's concerning.
OK, changing alg to straw2 will rebalance ale PGs on all nodes ?
--
Regards,
Luk
next prev parent reply other threads:[~2016-12-29 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 15:07 problem with removing osd Łukasz Chrustek
2016-12-29 19:10 ` Sage Weil
2016-12-29 20:20 ` Łukasz Chrustek
2016-12-29 20:26 ` Sage Weil
2016-12-29 20:46 ` Łukasz Chrustek
2016-12-29 20:49 ` Sage Weil
2016-12-29 20:55 ` Łukasz Chrustek
2016-12-29 21:41 ` Sage Weil
2016-12-29 22:02 ` Łukasz Chrustek [this message]
2016-12-29 22:18 ` Sage Weil
2016-12-29 23:13 ` Brad Hubbard
2016-12-29 23:33 ` Łukasz Chrustek
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=10710520745.20161229230211@tlen.pl \
--to=skidoo@tlen.pl \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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