[Bugs] [Bug 1173414] New: glusterd: remote locking failure when multiple synctask transactions are run

bugzilla at redhat.com bugzilla at redhat.com
Fri Dec 12 05:10:02 UTC 2014


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

            Bug ID: 1173414
           Summary: glusterd: remote locking failure when multiple
                    synctask transactions are run
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:

When two volume set operations are run in two different volumes simultaneously
in a loop some volume set transactions fail with a remote lock failure. 

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

How reproducible:
Always

Steps to Reproduce:
1. Setup a 2 node cluster
2. Create two volumes say vol1 & vol2  & start them
3. Run following script from any one of the node in the cluster
for i in {1..10} 
do
gluster v set vol1 diagnostics.client-log-level DEBUG &
gluster v set vol2 features.barrier on
done

Actual results:
Some of the transaction fails saying "Locking failed in <Peer node>, Please
check log file for details"

Expected results:
Local locking might fail, but remote locking should never fail here.

Additional info:

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


More information about the Bugs mailing list