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

Bug 1272030

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:	mainline	CC:	13965432176, bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-v4.1.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1540438 (view as bug list)		Environment:
Last Closed:	2018-06-20 17:56:51 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:
Bug Blocks:	1540438

Description Anoop C S 2015-10-15 10:15:48 UTC

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:

Comment 1 Vijay Bellur 2015-10-15 10:18:34 UTC

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)

Comment 2 Vijay Bellur 2015-10-15 12:30:09 UTC

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)

Comment 3 Vijay Bellur 2015-10-17 10:33:25 UTC

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)

Comment 4 Vijay Bellur 2015-10-17 16:50:19 UTC

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)

Comment 5 Vijay Bellur 2015-10-17 16:58:15 UTC

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)

Comment 6 Vijay Bellur 2015-10-19 04:47:08 UTC

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)

Comment 7 Vijay Bellur 2016-02-05 05:47:33 UTC

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)

Comment 8 Vijay Bellur 2016-03-09 05:36:10 UTC

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)

Comment 9 Vijay Bellur 2016-03-19 05:04:01 UTC

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)

Comment 10 Mike McCune 2016-03-28 22:15:42 UTC

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

Comment 11 Vijay Bellur 2016-06-15 16:55:27 UTC

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)

Comment 12 Worker Ant 2016-09-08 05:37:15 UTC

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)

Comment 13 Anoop C S 2016-09-08 05:41:15 UTC

AFR lock healing design specifications:

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

Comment 14 Worker Ant 2017-02-11 06:07:41 UTC

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)

Comment 15 Worker Ant 2017-02-11 06:25:59 UTC

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)

Comment 16 Worker Ant 2017-02-13 15:49:05 UTC

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)

Comment 17 Worker Ant 2017-02-14 06:44:56 UTC

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)

Comment 18 Worker Ant 2017-07-28 10:25:25 UTC

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)

Comment 19 Worker Ant 2018-01-29 17:36:58 UTC

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 20 Shyamsundar 2018-06-20 17:56:51 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-v4.1.0, please open a new bug report.

glusterfs-v4.1.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-June/000102.html
[2] https://www.gluster.org/pipermail/gluster-users/