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

[bugzilla at redhat.com]

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

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



+++ This bug was initially created as a clone of Bug #1708156 +++

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


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1708156
[Bug 1708156] ec ignores lock contention notifications for partially acquired
locks
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.