Dear Cephers, Enabling Ceph mirroring means double writes on the same data pool, thus possibly degrading the write performance dramatically. By google searching, i found the following words (apparently appeared several year ago)
"The rbd CLI allows you to use the "--journal-pool" argument when creating, copying, cloning, or importing and image with journaling enabled. You can also specify the journal data pool when dynamically enabling the journaling feature using the same argument. Finally, there is a Ceph config setting of "rbd journal pool = XYZ" that allows you to default new journals to a specific pool." Does anyone really have experience of using a specific SSD/NVMe pool to offload journaling workload from the data pool for RBD Mirroring disaster recovery? what would the best practice for improving performance of rbd mirroring (large amounts of data)? best regards, samuel huxia...@horebdata.cn _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
