[Bugs] [Bug 1384388] New: clean posix locks based on client-id as part of server_connection_cleanup

bugzilla at redhat.com bugzilla at redhat.com
Thu Oct 13 08:40:44 UTC 2016


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

            Bug ID: 1384388
           Summary: clean posix locks based on client-id as part of
                    server_connection_cleanup
           Product: GlusterFS
           Version: 3.9
         Component: locks
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: spalai at redhat.com
                CC: bugs at gluster.org, nbalacha at redhat.com,
                    sarumuga at redhat.com
        Depends On: 1338593



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

Description of problem:
  Currently posix locks are removed based on the fd number in case of a server
disconnect event. Post lock migration, the locks will not have any fd
association on destination. Hence, posix locks need to be removed based on
client-id.

--- Additional comment from Vijay Bellur on 2016-05-23 11:20:15 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-id for cleanup) posted (#1) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Vijay Bellur on 2016-06-13 15:40:30 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#2) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Vijay Bellur on 2016-08-01 10:47:32 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#3) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Worker Ant on 2016-09-14 12:40:58 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#4) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Worker Ant on 2016-09-20 13:39:28 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#5) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Worker Ant on 2016-09-20 17:56:34 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#6) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Worker Ant on 2016-09-27 18:44:36 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#7) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Worker Ant on 2016-09-27 18:49:40 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#8) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Worker Ant on 2016-09-28 08:07:50 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#9) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Worker Ant on 2016-10-03 15:27:08 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#10) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Worker Ant on 2016-10-03 15:53:55 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#11) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Worker Ant on 2016-10-03 16:03:51 MVT ---

REVIEW: http://review.gluster.org/14492 (posix/locks: associate posix locks
with client-uuid) posted (#12) for review on master by Susant Palai
(spalai at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1338593
[Bug 1338593] clean posix locks based on client-id as part of
server_connection_cleanup
-- 
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