Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1540438

Summary:	Remove lock recovery logic from client and server protocol translators
Product:	[Community] GlusterFS	Reporter:	Anoop C S <anoopcs>
Component:	protocol	Assignee:	Anoop C S <anoopcs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1272030	Environment:
Last Closed:	2018-03-15 11:26:04 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:	1272030
Bug Blocks:

Description Anoop C S 2018-01-31 04:54:24 UTC

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

Description of problem:
Remove lock replay/recovery logic related code from both client and server protocols. Plan is to implement the same with some modifications from AFR level which has a better view of server side.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Vijay Bellur on 2015-10-15 15:48:34 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server[WIP]) posted (#1) for review on master by Anoop C S (anoopcs)

--- Additional comment from Vijay Bellur on 2015-10-15 18:00:09 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server[WIP]) posted (#2) for review on master by Anoop C S (anoopcs)

--- Additional comment from Vijay Bellur on 2015-10-17 16:03:25 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server[WIP]) posted (#3) for review on master by Anoop C S (anoopcs)

--- Additional comment from Vijay Bellur on 2015-10-17 22:20:19 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server[WIP]) posted (#4) for review on master by Anoop C S (anoopcs)

--- Additional comment from Vijay Bellur on 2015-10-17 22:28:15 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server[WIP]) posted (#5) for review on master by Anoop C S (anoopcs)

--- Additional comment from Vijay Bellur on 2015-10-19 10:17:08 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server[WIP]) posted (#6) for review on master by Anoop C S (anoopcs)

--- Additional comment from Vijay Bellur on 2016-02-05 11:17:33 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server[WIP]) posted (#7) for review on master by Anoop C S (anoopcs)

--- Additional comment from Vijay Bellur on 2016-03-09 11:06:10 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server) posted (#8) for review on master by Anoop C S (anoopcs)

--- Additional comment from Vijay Bellur on 2016-03-19 10:34:01 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server) posted (#9) for review on master by Anoop C S (anoopcs)

--- Additional comment from Mike McCune on 2016-03-29 03:45:42 IST ---

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

--- Additional comment from Vijay Bellur on 2016-06-15 22:25:27 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server) posted (#10) for review on master by Anoop C S (anoopcs)

--- Additional comment from Worker Ant on 2016-09-08 11:07:15 IST ---

REVIEW: http://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server) posted (#11) for review on master by Anoop C S (anoopcs)

--- Additional comment from Anoop C S on 2016-09-08 11:11:15 IST ---

AFR lock healing design specifications:

https://docs.google.com/document/d/1py5uDvvbbL3piEnuCa_vo37Kq_vZzHhzKgnc2OiGzg8/edit?pli=1#heading=h.2vntu84m9e2j

--- Additional comment from Worker Ant on 2017-02-11 11:37:41 IST ---

REVIEW: https://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server) posted (#12) for review on master by Anoop C S (anoopcs)

--- Additional comment from Worker Ant on 2017-02-11 11:55:59 IST ---

REVIEW: https://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server) posted (#13) for review on master by Anoop C S (anoopcs)

--- Additional comment from Worker Ant on 2017-02-13 21:19:05 IST ---

REVIEW: https://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server) posted (#14) for review on master by Anoop C S (anoopcs)

--- Additional comment from Worker Ant on 2017-02-14 12:14:56 IST ---

REVIEW: https://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server) posted (#15) for review on master by Anoop C S (anoopcs)

--- Additional comment from Worker Ant on 2017-07-28 15:55:25 IST ---

REVIEW: https://review.gluster.org/12363 (protocol: Remove lock recovery logic from client and server) posted (#16) for review on master by Anoop C S (anoopcs)

--- Additional comment from Worker Ant on 2018-01-29 23:06:58 IST ---

COMMIT: https://review.gluster.org/12363 committed in master by "Raghavendra G" <rgowdapp> with a commit message- protocol: Remove lock recovery logic from client and server

Change-Id: I27f5e1e34fe3eac96c7dd88e90753fb5d3d14550
BUG: 1272030
Signed-off-by: Anoop C S <anoopcs>

Comment 1 Worker Ant 2018-01-31 04:56:09 UTC

REVIEW: https://review.gluster.org/19392 (protocol: Remove lock recovery logic from client and server) posted (#1) for review on release-4.0 by Anoop C S

Comment 2 Worker Ant 2018-01-31 16:17:28 UTC

COMMIT: https://review.gluster.org/19392 committed in release-4.0 by "Anoop C S" <anoopcs> with a commit message- protocol: Remove lock recovery logic from client and server

Change-Id: I27f5e1e34fe3eac96c7dd88e90753fb5d3d14550
BUG: 1540438
Signed-off-by: Anoop C S <anoopcs>
(cherry picked from commit 3e78ea991b213422fc423ff94994e1eb295569c7)

Comment 3 Shyamsundar 2018-03-15 11:26:04 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-4.0.0, please open a new bug report.

glusterfs-4.0.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/