As reported over here: https://bugzilla.redhat.com/show_bug.cgi?id=1002556
tl;dr:
1. Have a replicated volume (tested on 3.3 and 3.4)
2. Add a brick
3. Remove that brick
4. Restart gluster
5. Volume is slightly broken
Just using simple adding and removing, we end up with a broken volume that
behaves pretty non-deterministic.
We're trying to get the setup automated, so this is pretty much a blocker for
us :(
Has anybody else seen this behaviour?
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
