Scott,
We have identified a grey area in the code which is causing this issue.
FYI, fix has been sent in master - http://review.gluster.org/#/c/9269/
Once this patch is in master streamline I will backport it in 3.6 branch.
~Atin
On 12/12/2014 08:28 PM, Scott Merrill wrote:
On 11/25/14, 10:11
Hi,
I have a large volume that I want to geo-replicate using Gluster ( 1Tb). I
have the data rsynced on both servers and up to date. Can I start a
geo-replication session without having to send the whole contents over the wire
to the slave, since it's already there? I'm running Gluster 3.6.1.
Hi again,
I had a hard time to configure geo-replication. After creating the session, the
start gave me faulty state and I had to deal with it, it was the
/nonexistent/gsyncd in
/var/lib/glusterd/geo-replication/data1_node3.example_data2/gsyncd.conf to
change to /usr/libexec/gluster/gsyncd
