[Gluster-devel] Release 3.12: Glusto run status
spandura at redhat.com
Wed Aug 30 10:49:50 UTC 2017
1) remove-brick when IO is in progress. (i,e remove-brick state)
2) Immediately triggered remove-brick status. (no delay b/w remove-brick
start and status)
3) wait_for_rebalance_to_complete ( This get's the xml output of rebalance
status and keep checking for rebalance status to be 'complete' for every 10
seconds uptil 5 minutes. time out can be passed as parameter )
On Wed, Aug 30, 2017 at 3:39 PM, Shwetha Panduranga <spandura at redhat.com>
> 1) add-brick when IO is in progress , wait for 30 seconds
> 2) Trigger rebalance
> 3) Execute: 'rebalance status' ( there is no time delay b/w 2) and 3) )
> 4) wait_for_rebalance_to_complete ( This get's the xml output of rebalance
> status and keep checking for rebalance status to be 'complete' for every 10
> seconds uptil 5 minutes. 5 minutes wait time can be passed as parameter )
> At every step we check the exit status of the command output. If the exit
> status is non-zero we fail the test case.
> On Wed, Aug 30, 2017 at 6:06 AM, Sankarshan Mukhopadhyay <
> sankarshan.mukhopadhyay at gmail.com> wrote:
>> On Wed, Aug 30, 2017 at 6:03 AM, Atin Mukherjee <amukherj at redhat.com>
>> > On Wed, 30 Aug 2017 at 00:23, Shwetha Panduranga <spandura at redhat.com>
>> > wrote:
>> >> Hi Shyam, we are already doing it. we wait for rebalance status to be
>> >> complete. We loop. we keep checking if the status is complete for '20'
>> >> minutes or so.
>> > Are you saying in this test rebalance status was executed multiple times
>> > till it succeed? If yes then the test shouldn't have failed. Can I get
>> > access the complete set of logs?
>> Would you not prefer to look at the specific test under discussion as
>> Gluster-devel mailing list
>> Gluster-devel at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-devel