You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, we're setting up (testing actually) geo-replication with gluster.
We'd like to copy all our data, about 150TB.
In order to speed things up, we'd like to start copying with a regular rsync a certain directory which is about 100TB.
The thing is, from what we've tested, geo-replication overwrites files despite them being the same (same route, same checksum). This would mean copying that directory beforehand would be useless.
Is there any way to prevent this? Like a flag or something that forces gluster to read checksum before overwriting it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello everyone!
So, we're setting up (testing actually) geo-replication with gluster.
We'd like to copy all our data, about 150TB.
In order to speed things up, we'd like to start copying with a regular rsync a certain directory which is about 100TB.
The thing is, from what we've tested, geo-replication overwrites files despite them being the same (same route, same checksum). This would mean copying that directory beforehand would be useless.
Is there any way to prevent this? Like a flag or something that forces gluster to read checksum before overwriting it?
Thank you all in advanced
PS: Pardon my english, not my mother tongue
Beta Was this translation helpful? Give feedback.
All reactions