[Bugs] [Bug 1800522] New: Often getting "Locking failed on <node>. Please check log file for details."

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1800522

            Bug ID: 1800522
           Summary: Often getting "Locking failed on <node>. Please check
                    log file for details."
           Product: GlusterFS
           Version: 6
          Hardware: x86_64
                OS: Linux
            Status: NEW
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: lars.berntzon at cecilia-data.se
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:
Running the command "gluster volume status <volume>" on two separate nodes
often gives the error:
   Locking failed on <node>. Please check log file for details.


Version-Release number of selected component (if applicable):

Ubuntu 18 running gluster 6.7-ubuntu1~bionic1

How reproducible:

Easy.


Steps to Reproduce:

1. Run a while loop on first gluster nodes like:
      while :; do gluster volume status <volume>; done

2. Run same loop on other node simultaneously.

Actual results:

Both loops will start to randomly fail with the message:
      Locking failed on <node>. Please check log file for details.


Expected results:
   Status reports on both nodes.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.