15 Feb
2023
15 Feb
'23
8:43 a.m.
Hi,
I haven't done this in a production cluster yet, only in small test
clusters without data. But there's a rename-bucket command:
ceph osd crush rename-bucket <srcname> <dstname>
rename bucket <srcname> to <dstname>
It should do exactly that, just rename the bucket within the crushmap
without changing the ID. That command also exists in Luminous, I
believe. To have an impression of the impact I'd recommend to test in
a test cluster first.
Regards,
Eugen
Zitat von Manuel Lausch <manuel.lausch(a)1und1.de>de>:
Hi,
yes you can rename a node without massive rebalancing.
The following I tested with pacific. But I think this should work with
older versions as well.
You need to rename the node in the crushmap between shutting down the
node with the old name and starting it with the new name.
You only must keep the ID from the node in the crushmap!
Regards
Manuel
On Mon, 13 Feb 2023 22:22:35 +0000
"Rice, Christian" <crice(a)pandora.com> wrote:
Can anyone please point me at a doc that explains
the most
efficient procedure to rename a ceph node WITHOUT causing a massive
misplaced objects churn?
When my node came up with a new name, it properly joined the
cluster and owned the OSDs, but the original node with no devices
remained. I expect this affected the crush map such that a large
qty of objects got reshuffled. I want no object movement, if
possible.
BTW this old cluster is on luminous. ☹
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io