Change crush rule on pool
Hi I would like to change the crush rule so data lands on ssd instead of hdd, can this be done on the fly and migration will just happen or do I need to do something to move data? Jesper Sent from myMail for iOS
If you create the new rule, and set the pool in question to it, then data movement will begin automatically. Be warned this might increase your load for a long time. On Wed, Aug 5, 2020 at 12:20 PM <jesper@krogh.cc> wrote:
Hi
I would like to change the crush rule so data lands on ssd instead of hdd, can this be done on the fly and migration will just happen or do I need to do something to move data?
Jesper
Sent from myMail for iOS _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
I would like to change the crush rule so data lands on ssd instead of hdd, can this be done on the fly and migration will just happen or do I need to do something to move data?
I would actually like to relocate my object store to a new storage tier. Is the best to: 1) create new pool on storage tier (SSD) 2) stop activity 3) rados cppool data to the new one. 4) rename the pool back into the "default.rgw.buckets.data" pool. Done? Thanks.
If you have capacity to have both online at the same time, why not add the SSDs to the existing pool, let the cluster converge, then remove the HDDs? Either all at once or incrementally? With care you’d have zero service impact. If you want to change the replication strategy at the same time, that would be more complex. — Anthony
On Sep 12, 2020, at 12:42 AM, jesper@krogh.cc wrote:
I would like to change the crush rule so data lands on ssd instead of hdd, can this be done on the fly and migration will just happen or do I need to do something to move data?
I would actually like to relocate my object store to a new storage tier. Is the best to:
1) create new pool on storage tier (SSD) 2) stop activity 3) rados cppool data to the new one. 4) rename the pool back into the "default.rgw.buckets.data" pool.
Done?
Thanks. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Can i do that - when the SSDs are allready used in another crush rule - backing and kvm_ssd rbd’s? Jesper Sent from myMail for iOS Saturday, 12 September 2020, 11.01 +0200 from anthony.datri@gmail.com <anthony.datri@gmail.com>:
If you have capacity to have both online at the same time, why not add the SSDs to the existing pool, let the cluster converge, then remove the HDDs? Either all at once or incrementally? With care you’d have zero service impact. If you want to change the replication strategy at the same time, that would be more complex.
— Anthony
On Sep 12, 2020, at 12:42 AM, jesper@krogh.cc wrote:
I would like to change the crush rule so data lands on ssd instead of hdd, can this be done on the fly and migration will just happen or do I need to do something to move data?
I would actually like to relocate my object store to a new storage tier. Is the best to:
1) create new pool on storage tier (SSD) 2) stop activity 3) rados cppool data to the new one. 4) rename the pool back into the "default.rgw.buckets.data" pool.
Done?
Thanks. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
participants (3)
-
Anthony D'Atri
-
jesper＠krogh.cc
-
Nathan Fish