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:
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)
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)
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)
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)
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)
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)
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)
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)
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)
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
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)
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)
AFR lock healing design specifications: https://docs.google.com/document/d/1py5uDvvbbL3piEnuCa_vo37Kq_vZzHhzKgnc2OiGzg8/edit?pli=1#heading=h.2vntu84m9e2j
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)
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)
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)
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)
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)
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>
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/