VISHAL PANDEY

@aravindavk If we are to implement this, should we add probing peer using hostname as well since we are just considering addresses currently ?

@Madhu-1 The above call for setting the brick-multiplex on, doesn't exist. The call should be - curl -XPOST http://localhost:24007/v1/cluster/options -d '{"options":{"cluster.brick-multiplex": "on"}}' I will also add the validation for setting...

The thin-arbiter support has now been introduced in glusterd.

@Madhu-1 @rishubhjain Its because the client process keeps on sending the RPC request to GD2 for the bricks until its sucessful. I guess there must have been a failure mounting...

@rishubhjain I dont think we can avoid continuous RPC requests in case of a failure but what we can do is we can limit memory leakage, which I think @harigowtham...

@rishubhjain This happens sometimes. But, I have seen this error only during CI builds, Its very rare in my local as well. But retrigger the build and it will pass.

https://github.com/gluster/glusterd2/issues/1090

@Madhu-1 Any updates regarding this issue ?

@Shrivaibavi I have a few Questions : 1- Do we need to provide volume name as well in the above two commands ? 2- I tried to run the command...

@atinmu This is due to delay in brick SignIn i believe. @PrasadDesala Can you give the bricks some more time and check after a while if the brick still shows...