Re: [Gluster-devel] gluster volume stop and the regressions

The volume stop, in brick-mux mode reveals a race with my patch [1] Although this behavior is 100% reproducible with my patch, this, by no means, implies that my patch is buggy. In brick-mux mode, during volume stop, when glusterd sends a brick-detach message to the brick process for the last

Re: [Gluster-devel] gluster volume stop and the regressions

On 1 February 2018 at 09:46, Milind Changire wrote: > If a *volume stop* fails at a user's production site with a reason like > *rebalance session is active* then the admin will wait for the session to > complete and then reissue a *volume stop*; > > So, in essence, the

Re: [Gluster-devel] gluster volume stop and the regressions

I don't think that's the right way. Ideally the test shouldn't be attempting to stop a volume if rebalance session is in progress. If we do see such a situation even with we check for rebalance status and wait till it finishes for 30 secs and still volume stop fails with rebalance session in