Atin Mukherjee
Atin Mukherjee
As @kshlm seems to be busy on the transaction framework enhancements for GCS-Sprint1, I don't see this issue to move forward for the current sprint. @kshlm Is there any code...
Quick user guide vs user guide - what difference in the content makes these two documents meaningful?
I believe this will be automatically taken care of when brick multiplexing PR is merged. This will just be a test effort. @rafikc30 @vpandey-RH
@Akarsha-rai can you provide the volume info output please? Did we have any bricks of the volume hosted on the node which was down?
I'm trying to hunt down for the reason of making such behaviour in GD1.
Here's the GD1 behavior: After the volume stop goes through when GD1/node goes down on one of the nodes, after GD1/node comes back online, the brick process is brought down.
@aravindavk I still think functionality wise we should disallow volume stop if a node/glusterd service hosting any of the bricks is down. For eg - If have a distribute only...
Are we able to reproduce this with latest deployment?
@phlogistonjohn Would we be able to complete this in a week's time or do you want me to move this to Sprint 2?
We need to enhance https://github.com/sosreport/sos/blob/master/sos/plugins/gluster.py to ensure (a) glusterd2 log path is covered & (b) all the required commands are successfully triggered with glustercli. The plugin has to work based...