Red Hat Bugzilla – Bug 1275972
Dist-geo-rep: Support geo-replication to work with sharding
Last modified: 2016-03-22 04:15:25 EDT
+++ This bug was initially created as a clone of Bug #1265148 +++
Description of problem:
This bug tracks all the changes required for geo-replication to work with
Requirements as per design:
1. Both master and slave should be sharded
2. Sharding configurations should be retained same as in master
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Geo-replication does not work with sharding
Geo-replication should work with sharding.
REVIEW: http://review.gluster.org/12438 (features/shard: Support geo-rep for sharded volume) posted (#1) for review on release-3.7 by Kotresh HR (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/12438 committed in release-3.7 by Pranith Kumar Karampuri (email@example.com)
Author: Kotresh HR <firstname.lastname@example.org>
Date: Thu Sep 24 15:42:14 2015 +0530
features/shard: Support geo-rep for sharded volume
Shard xlator on slave side is by passed for all the fops
to geo-rep mount. So each shard on master is considered as a
separate file for geo-rep and it syncs them separately on to
slave. The extended attribute in which shard maintains the
size is also synced from master and shard on slave doesn't
calculate by itself.
1. If master is sharded volume, slave also should be sharded.
2. Slave's shard configurations should be same as master.
3. Geo-rep config of xattr sync should not be disabled.
All other dependant patches:
Tested-by: NetBSD Build System <email@example.com>
Reviewed-by: Krutika Dhananjay <firstname.lastname@example.org>
Reviewed-by: Pranith Kumar Karampuri <email@example.com>
Signed-off-by: Kotresh HR <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
All other 3.7 dependent patches for geo-rep interop with sharding: