Hello. Based on https://bugzilla.redhat.com/show_bug.cgi?id=1077452, it looks like non-root Geo-replication is broken in 3.5.0. Commits have been made to fix non-root Geo-replication, but they haven't been included in a release yet. Can anyone provide insight into whether release 3.5.1 should include those fixes or not, and when 3.5.1, or a release incorporating the fixes, might be available? Here's why I'm interested. We've got a working gluster 3.5.0 cluster of 2 nodes that has active gluster volumes used in production. Now we'd like to setup Geo-replication. We wanted to take advantage of the new distributed Geo-Replication provided by v 3.5.0, but have run into some difficulties. We want to use the mountbroker for slaves so we can use a non-root account on the slaves for replication. At this point I think we need to either: 1) wait for 3.5.1 (or later) to try implementing non-root distributed Geo-replication OR 2) try down-grading to 3.4.3 and use non-root Geo-replication (non-distributed) Knowing when non-root distributed Geo-replication setup is expected to work will help us make that decision. Also, is 3.5.0 backward compatible with 3.4.3, in that we'd be able to safely replace the installed 3.5.0 packages on our gluster servers with 3.4.3 packages without risking data corruption? Worst case I can always move the data elsewhere temporarily, down-grade gluster to 3.4.3, create new volumes and move the data back. That'll be very time consuming, though, so I'd like to avoid it if I can. Thanks for any insight you can provide, folks. Doug -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140618/9753d4af/attachment.html>