Gluster users - May 2016 - geo-replication going offline in 3.5 and 3.6 with 30 days

Hi Brian,

Thanks for reporting the issue.

Could you please post the geo-replication logs?
It would help us find out why geo-replication has failed to sync.

You can find master geo-rep logs under /var/log/glusterfs/geo-replication
and slave logs under /var/log/glusterfs/geo-replication-slaves

Thanks and Regards,
Kotresh H R

----- Original Message -----
> From: "Brian Litzinger" <brian at worldcontrol.com>
> To: gluster-users at gluster.org
> Sent: Saturday, April 30, 2016 2:01:14 AM
> Subject: [Gluster-users] geo-replication going offline in 3.5 and 3.6 with
30 days
> 
> Sorry if this is a double post.
> 
> I ran geo-replication with gluster 3.4 for about a year without any issues.
> 
> I have tried the same setup with 3.5 and 3.6 (with gluster volumes at
> both end) and in both cases the geo-replication failed silently within
about
> 30 days.
> 
> The various gluster status commands reported that all was well in 3.5 and
> 3.6,
> but the data was no longer geo-replicating.
> 
> Looking in the logs and when the geo-replication was no longer reflected in
> the
> geo-replica filesystem this line from the logs looks suspicious:
> 
> (this was 7 days after the geo-replication had been started)
> 
> [2016-04-11 16:04:37.997284] E [iobuf.c:733:iobuf_unref]
> (-->/usr/local/lib/libglusterfs.so.0(call_resume+0x5cc) [0x7f168605c6fc]
> (-->/usr/local/lib/libglusterfs.so.0(default_readv_resume+0x14c)
> [0x7f1686042d1c]
>
(-->/usr/local/lib/glusterfs/3.5.9/xlator/performance/quick-read.so(qr_readv+0x4c)
> [0x7f167b7d126c]))) 0-iobuf: invalid argument: iobuf
> 
> [2016-04-11 16:04:37.997314] E [iobuf.c:839:iobref_unref]
> (-->/usr/local/lib/libglusterfs.so.0(call_resume+0x5cc) [0x7f168605c6fc]
> (-->/usr/local/lib/libglusterfs.so.0(default_readv_resume+0x14c)
> [0x7f1686042d1c]
>
(-->/usr/local/lib/glusterfs/3.5.9/xlator/performance/quick-read.so(qr_readv+0x4c)
> [0x7f167b7d126c]))) 0-iobuf: invalid argument: iobref
> 
> Some of the issues worth exploring are:
> 
> 1) Why did it stop geo-replicating?
> 
> 2) Why was this failure not reflected in the status commands?
> 
> 3) Should I stick with 3.4 until the "production" label is
>    applied to a later version?
> 
> --
> brian
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>