[Bugs] [Bug 1708156] New: ec ignores lock contention notifications for partially acquired locks

bugzilla at redhat.com bugzilla at redhat.com
Thu May 9 09:04:57 UTC 2019


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

            Bug ID: 1708156
           Summary: ec ignores lock contention notifications for partially
                    acquired locks
           Product: GlusterFS
           Version: mainline
            Status: NEW
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: jahernan at redhat.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:

When an inodelk is being acquired, it could happen that some bricks have
already granted the lock while others don't. From the point of view of ec, the
lock is not yet acquired.

If at this point one of the bricks that has already granted the lock receives
another inodelk request, it will send a contention notification to ec.

Currently ec ignores those notifications until the lock is fully acquired. This
means than once ec acquires the lock on all bricks, it won't be released
immediately when eager-lock is used.

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


How reproducible:

Very frequently when there are multiple concurrent operations on same directory

Steps to Reproduce:
1. Create a disperse volume
2. Mount it from several clients
3. Create few files on a directory
4. Do 'ls' of that directory at the same time from all clients

Actual results:

Some 'ls' take several seconds to complete

Expected results:

All 'ls' should complete in less than a second

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