Re: "ceph osd crush set|reweight-subtree" behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for finding this Mykola, it looks like a bug to me!

On 11/1/20 11:14 PM, Mykola Golub wrote:
The tracker ticket:

https://tracker.ceph.com/issues/48065

On Thu, Oct 29, 2020 at 12:29:52PM +0200, Mykola Golub wrote:
Hi,

We noticed that if one set an osd crush weight using the command

   ceph osd crush set $id $weight host=$host

it updates the osd weight on $host bucket, but does not update it on
the "class" bucket (${host}~hdd or ${host}~ssd), and as a result the
old weight is still used until one runs `ceph osd crush reweight-all`
or do some other changes that cause the crushmap recalculation.

The same behaviour is for `ceph osd crush reweight-subtree <name> <weight>`
command.

Is it expected behavior or should I report a bug to the tracker?

I would consider this is ok if I knew a way how to set a weight for a
"class" (xyz~hdd or ~ssd) bucket. When I try to use ${host}~ssd it
complains about invalid chars ~ in the bucket name.

--
Mykola Golub

_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx



[Index of Archives]     [CEPH Users]     [Ceph Devel]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux