[Gluster-users] glusterfs3.4.2-1 split-brain question

Fri Sep 25 02:18:44 UTC 2015

I have a 4 node distributed-replicated gluster farm.

Volume Name: devstatic
Type: Distributed-Replicate
Volume ID: 75832afb-f20e-4017-8d74-8550a92233fd
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Brick1: omhq1b4e:/static/content
Brick2: omdx1b50:/static/content
Brick3: omhq1b4f:/static/content
Brick4: omdx1b51:/static/content
Options Reconfigured:
features.quota-deem-statfs: on
server.allow-insecure: on
network.ping-timeout: 10
performance.lazy-open: off
performance.write-behind: on
features.quota: on
geo-replication.indexing: off
server.statedump-path: /tmp/
diagnostics.brick-log-level: CRITICAL

When I query heal split-brain info I get the following.

[root at omhq1b4e ~]# gluster volume heal devstatic info split-brain
Gathering list of split brain entries on volume devstatic has been 

Brick omhq1b4e:/static/content
Number of entries: 0

Brick omdx1b50:/static/content
Number of entries: 0

Brick omhq1b4f:/static/content
Number of entries: 43
at                    path on brick
2015-09-24 18:50:20 /
2015-09-24 18:50:20 /
2015-09-24 18:52:01 /
2015-09-24 19:10:22 /

Brick omdx1b51:/static/content
Number of entries: 42
at                    path on brick
2015-09-24 18:51:58 /
2015-09-24 18:51:59 /
2015-09-24 19:01:59 /
2015-09-24 19:11:59 /

Being / on the same replicate, how would I safely resolve this issue?  Is 
it really going to require me to delete the root of each node and heal?  I 
hope not, the entire volume is about 1TB.

Thank you,

Khoi Mai
Union Pacific Railroad
Distributed Engineering & Architecture
Senior Project Engineer


This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient.  Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law.  If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150924/bff2bc2d/attachment.html>

More information about the Gluster-users mailing list