Hide Forgot
Description of problem: ======================= GlusterD stopped working when i ran the two gluster commands parallel on two nodes cluster, on one node, executed a command peer probe&deprobing a node in loop and on other node executed a command gluster volume status in loop, after some time of execution, glusterd stopped running on the probing/deprobing node. probing commands failed with error message: peer probe: success. peer detach: success peer probe: failed: Error through RPC layer, retry again later Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.7.5-19 How reproducible: ================= Every time Steps to Reproduce: =================== 1.Have two nodes (node-1 and node-2) cluster with any type of volume. 2. Execute 2a and 2b on two nodes parallel 2a)On Node-1 execute the below command: >> for i in `seq 1 150`; do gluster peer probe <node-3>;gluster peer detach <node-3>;done 2b)On node-2: execute the below command: >> for i in `seq 1 200`;do gluster volume status; done 3. Observe the above two commands results Actual results: =============== GlusterD stopped running when executing two commands parallel. Expected results: ================= GlusterD should not stop running when commands are executed parallel. Additional info:
Steps look to be for negative testing and in production this would never be done. Gaurav has already started looking into it. Hence lowering down the severity and priority. Byreddy, Please attach the sosreport along with the core file from both the nodes. ~Atin
I will attach the sosreports
Created attachment 1128427 [details] Node-1-sosreport
Created attachment 1128428 [details] Node-2-sosreport
Created attachment 1128430 [details] Node-3-sosreport
We do not have any plan to work on this in near future as the use case mentioned here is something which will not be hit in any production set up. I am closing this bug right away. If you think otherwise, reopen with a justification.