Bug 1362387

Summary: nfs-ganesha server should flush locks when in grace
Product: [Community] GlusterFS Reporter: Soumya Koduri <skoduri>
Component: common-haAssignee: Soumya Koduri <skoduri>
Status: CLOSED DEFERRED QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: mainlineCC: atumball, bugs, pasik
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-11 02:17:16 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:

Description Soumya Koduri 2016-08-02 06:09:41 UTC
Description of problem:

In an Active-Active HA configuration, when VIP moves from one active server(A) to another active server(B), currently we put all the servers in grace. But the locks taken by server(A) from that VIP have to flushed as well at the backend glusterFS server in order for the client to reclaim their locks when connected to server(B).
    
NFS-Ganesha has a provision to flush the locks requested on a VIP using the same dbus signal used to put it in grace but with the event "EVENT_RELEASE_IP" whose enum value maps to '2'.


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 2016-08-02 06:41:40 UTC
REVIEW: http://review.gluster.org/15067 (common-ha: nfs-ganesha should flush locks when in grace) posted (#1) for review on master by soumya k (skoduri)

Comment 2 Amar Tumballi 2019-05-11 02:17:16 UTC
Any goals to fix this? If this is still an issue, mark it as DEFERRED, if fixed CLOSE it as CURRENTRELEASE/WORKSFORME.

Currently marking as DEFERRED as I have not heard about this in a long time.