Description of problem: With Heketi, when a volume is created with a large number of bricks ( > 300), glusterd timeouts volume start operation, during which there is race condition between heketi and glusterd operation. Version-Release number of selected component (if applicable): heketi-1.0.1-1.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a volume through heketi of a large size: In our case, it was 640G where 300+ bricks were created for a single gluster volume Actual results: Volume creation fails due to glusterd timeout. Additional info: A solution for the same is available upstream now: https://github.com/heketi/heketi/issues/248
This looks to me like a Glusterd issue that may be fixed in GlusterD 2.0.
Thank you for the bug report. This particular bug was fixed and a update package was published (RHGS 3.3.1+). Please feel free to report any further bugs you find, or make further reports if this bug is not fixed after you install the update.