REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave vol uuid to geo-rep session [WIP]) posted (#4) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave vol uuid to geo-rep session) posted (#6) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave vol uuid to geo-rep session) posted (#7) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave vol uuid to geo-rep session) posted (#8) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave vol uuid to geo-rep session) posted (#9) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave vol uuid to geo-rep session) posted (#10) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave vol uuid to geo-rep session) posted (#11) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave vol uuid in geo-rep session) posted (#12) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave vol uuid in geo-rep session) posted (#13) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave vol uuid in geo-rep session) posted (#14) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave volume uuid in geo-rep session) posted (#15) for review on master by Saravanakumar Arumugam (sarumuga)
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave volume uuid in geo-rep session) posted (#16) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave volume uuid in geo-rep session) posted (#17) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave volume uuid in geo-rep session) posted (#18) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave volume uuid in geo-rep session) posted (#19) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave volume uuid in geo-rep session) posted (#20) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave volume uuid in geo-rep session) posted (#21) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave volume uuid in geo-rep session) posted (#22) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: involve slave volume uuid in geo-rep session) posted (#23) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#24) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#25) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#26) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#27) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#28) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#29) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#30) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#31) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#32) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#33) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#34) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (geo-rep: slave volume uuid to identify a geo-rep session) posted (#35) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/13111 (glusterd/geo-rep: slave volume uuid to identify a geo-rep session) posted (#36) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/13111 (glusterd/geo-rep: slave volume uuid to identify a geo-rep session) posted (#37) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/13111 committed in master by Aravinda VK (avishwan) ------ commit a9128cda34b1f696b717ba09fa0ac5a929be8969 Author: Saravanakumar Arumugam <sarumuga> Date: Tue Dec 29 19:22:36 2015 +0530 glusterd/geo-rep: slave volume uuid to identify a geo-rep session Problem: Currently, it is possible to create multiple geo-rep session from the Master host to Slave host(s), where Slave host(s) belonging to the same volume. For example: Consider Master Host M1 having volume tv1 and Slave volume tv2, which spans across two Slave hosts S1 and S2. Currently, it is possible to create geo-rep session from M1(tv1) to S1(tv2) as well as from M1(tv1) to S2(tv2). When the Slave Host is alone modified, it is identified as a new geo-rep session (as slave host and slave volume together are identifying Slave side). Also, it is possible to create both root and non-root geo-rep session between same Master volume and Slave volume. This should also be avoided. Solution: This multiple geo-rep session creation must be avoided and in order to avoid, use Slave volume uuid to identify a Slave. This way, we can identify whether a session is already created for the same Slave volume and avoid creating again (using different host). When the session creation is forced in the above scenario, rename the existing geo-rep session directory with new Slave Host mentioned. Change-Id: I9239759cbc0d15dad63c48b8cf62950bb687c7c8 BUG: 1294813 Signed-off-by: Saravanakumar Arumugam <sarumuga> Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/13111 Reviewed-by: Kotresh HR <khiremat> Tested-by: Kotresh HR <khiremat> Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj> CentOS-regression: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/14372 (glusterd/geo-rep: slave volume uuid to identify a geo-rep session) posted (#1) for review on release-3.8 by Saravanakumar Arumugam (sarumuga)