Nothing but GlusterFS should be writing to bricks. Mount a client
and write there.
On 01/26/2015 01:38 PM, Tiago Santos
wrote:
Right.
I have Brick1 being constantly written. But I have nothing
writing on Brick2. It just get "healed" data from Brick1.
This setup is still not in production, and there's no
applications using that data. I have rsyncs constantly
updating Brick1 (bring data from production servers), and then
Gluster updates Brick2.
Which makes me wonder how may I be creating multiple
replicas during a split-brain.
It may be the case that, having a split-brain event, I may
be updating versions of the same file on Brick1 (only), and
Gluster understands it as different versions and things get
confuse?
Anyways, while we talk I'm gonna run Joe's precious
procedure on split-brain recovery.
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users