[Bugs] [Bug 1800522] 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

Sanju <srakonde at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
                 CC|                            |srakonde at redhat.com
         Resolution|---                         |NOTABUG
           Assignee|bugs at gluster.org            |srakonde at redhat.com
           Doc Type|---                         |If docs needed, set a value
        Last Closed|                            |2020-02-10 04:07:44



--- Comment #1 from Sanju <srakonde at redhat.com> ---
"gluster volume status" collects information from all the nodes to display the
output on the originator node. So, it needs the lock on every node. When we
execute this command simultaneously on different nodes of trusted storage pool,
the locking fails and the error is expected.

Hence, closing the bug as not a bug.

Thanks,
Sanju

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