[Bugs] [Bug 1540438] New: Remove lock recovery logic from client and server protocol translators

bugzilla at redhat.com bugzilla at redhat.com
Wed Jan 31 04:54:24 UTC 2018


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

            Bug ID: 1540438
           Summary: Remove lock recovery logic from client and server
                    protocol translators
           Product: GlusterFS
           Version: 4.0
         Component: protocol
          Severity: medium
          Priority: medium
          Assignee: bugs at gluster.org
          Reporter: anoopcs at redhat.com
                CC: bugs at gluster.org
        Depends On: 1272030



+++ 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com)

--- 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 at redhat.com> 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 at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1272030
[Bug 1272030] Remove lock recovery logic from client and server protocol
translators
-- 
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