Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1362387 - nfs-ganesha server should flush locks when in grace
Summary: nfs-ganesha server should flush locks when in grace
Keywords:
Status: POST
Alias: None
Product: GlusterFS
Classification: Community
Component: common-ha
Version: mainline
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Soumya Koduri
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-02 06:09 UTC by Soumya Koduri
Modified: 2019-03-25 18:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.