Bug 1384388

Summary:	clean posix locks based on client-id as part of server_connection_cleanup
Product:	[Community] GlusterFS	Reporter:	Susant Kumar Palai <spalai>
Component:	locks	Assignee:	Susant Kumar Palai <spalai>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.9	CC:	bugs, nbalacha, sarumuga
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1338593	Environment:
Last Closed:	2017-03-08 12:33:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1338593
Bug Blocks:	1350744

Description Susant Kumar Palai 2016-10-13 08:40:44 UTC

+++ 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)

--- 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)

--- 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)

--- 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)

--- 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)

--- 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)

--- 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)

--- 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)

--- 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)

--- 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)

--- 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)

--- 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)

Comment 1 Susant Kumar Palai 2016-10-13 08:51:15 UTC

upstream master patch: http://review.gluster.org/#/c/14492

Comment 2 Kaushal 2017-03-08 12:33:11 UTC

This bug is getting closed because GlusterFS-3.9 has reached its end-of-life [1].

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please open a new bug against the newer release.

[1]: https://www.gluster.org/community/release-schedule/