Description of problem: When rebooting a gluster node the brick does not come online consistently. After several rounds of testing on 3.7.5 we see fewer than 50% that the brick comes online after a reboot. Nothing is logged, and restarting glusterd fixes the issue. It looks like maybe a timing issue? Unfortunately this is a secure site, and no logs can be provided (even if they had anything to show). Version-Release number of selected component (if applicable):RHGS 3.1.2\glusterfs 3.7.5 How reproducible:50% Steps to Reproduce: 1.Reboot a running gluster node. (simulating failure). 2.Check gluster volume status Actual results:Often brick(s) are still down. # gluster volume status test-volume Status of volume: test-volume Gluster process Port Online Pid ------------------------------------------------------------ Brick arch:/export/rep1 24010 Y 18474 Brick arch:/export/rep2 24011 N Expected results:All bricks are online after reboot # gluster volume status test-volume Status of volume: test-volume Gluster process Port Online Pid ------------------------------------------------------------ Brick arch:/export/rep1 24010 Y 18474 Brick arch:/export/rep2 24011 Y 18479
We need some more details. Could you please provide the output of following commands: gluster peer status gluster volume info Were you running a single node cluster, if not which node did you reboot?
Can we get the details sought for in comment 2?
I am closing this BZ as we didn't have sufficient data for analysing this issue.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days