Hallo,I have the same issue as mentioned here, namely converting/migrating a replicated pool to an EC-based one. I have ~20 TB so my problem is far easier, but I'd like to perform this operation without introducing any downtime (or possibly just a minimal one, to rename pools).
I am using Luminous 12.2.8 on CentOS 7.5, currently.
I am planning to use the procedure outlined in the article quoted below, integrated with the trick described here (to force promotion of each object to the cache) at point 2)
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2017-February/016109.html
I don't mind some manual intervention nor the procedure taking long
time: my only question is...
Is the above procedure data-safe, in principle?Additional question: while doing the migration, people may create or remove objects, so I am wondering how can I make sure that the migration is complete? For sure, comparing numbers of objects in the old/new pools won't be the way, right?
Thanks for your help
Fulvio
On 10/26/2018 03:37 PM, Matthew Vernon wrote:
Hi, On 26/10/2018 12:38, Alexandru Cucu wrote:Have a look at this article:> https://ceph.com/geen-categorie/ceph-pool-migration/Thanks; that all looks pretty hairy especially for a large pool (ceph df says 1353T / 428,547,935 objects)... ...so something a bit more controlled/gradual and less manual-error-prone would make me happier! Regards, Matthew _______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
