search for: 73279c4f112b

Hi folks, I'm running a simple gluster setup with a single volume replicated at two servers, as follows: Volume Name: gv0 Type: Replicate Volume ID: dd4996c0-04e6-4f9b-a04e-73279c4f112b Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: sst0:/var/glusterfs Brick2: sst2:/var/glusterfs Options Reconfigured: cluster.self-heal-daemon: enable performance.readdir-ahead: on nfs.disable: on transport.address-family: inet This volume is used...

...ontrol.ru/) +7 916 172 6 170 August 1, 2017 12:29 AM, "WK" wrote: On 7/31/2017 1:12 AM, Seva Gluschenko wrote: Hi folks, I'm running a simple gluster setup with a single volume replicated at two servers, as follows: Volume Name: gv0 Type: Replicate Volume ID: dd4996c0-04e6-4f9b-a04e-73279c4f112b Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2 Transport-type: tcp The problem is, when it happened that one of replica servers hung, it caused the whole glusterfs to hang. Yes, you lost quorum and the system doesn't want you to get a split-brain. Could you please drop me a h...