Bug 1213752 - nfs-ganesha: Multi-head nfs need Upcall Cache invalidation support
Summary: nfs-ganesha: Multi-head nfs need Upcall Cache invalidation support
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: ganesha-nfs
Version: mainline
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Soumya Koduri
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1218858
TreeView+ depends on / blocked
 
Reported: 2015-04-21 08:36 UTC by Soumya Koduri
Modified: 2016-06-16 12:53 UTC (History)
0 users

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1218858 (view as bug list)
Environment:
Last Closed: 2016-06-16 12:53:42 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Soumya Koduri 2015-04-21 08:36:30 UTC
Description of problem:

Multi-Head NFS-Ganesha servers need upcall (cache-invalidation) support to notify them incase of any changes to the files in the backend.

Hence, upcall xlator option "features.cache-invalidation" needs to be enabled while trying to bring up/configure nfs-ganesha server via Gluster CLI.

Comment 1 Anand Avati 2015-05-05 12:59:40 UTC
REVIEW: http://review.gluster.org/10581 (Cache-invalidation : set to on/off depending on ganesha.enable value) posted (#1) for review on master by Meghana M (mmadhusu)

Comment 2 Anand Avati 2015-05-05 19:47:05 UTC
COMMIT: http://review.gluster.org/10581 committed in master by Kaleb KEITHLEY (kkeithle) 
------
commit a5fc34604aef973606431bf7d873abb91ee03d5a
Author: Meghana Madhusudhan <mmadhusu>
Date:   Tue May 5 18:19:51 2015 +0530

    Cache-invalidation : set to on/off depending on ganesha.enable value
    
    Multi-Head NFS-Ganesha servers need upcall (cache-invalidation)
    support to notify them in case of any changes to the files in the backend.
    Hence, upcall xlator option "features.cache-invalidation" needs to be enabled
    when ganesha.enable is set to 'on'. Similarly, this feature needs
    to be disabled when ganesha.enable is set to 'off'
    Signed-off-by: Meghana Madhusudhan <mmadhusu>
    
    Change-Id: Ifdd1d50e48a2bd2a388f73c0b9e318c6092ac190
    BUG: 1213752
    Reviewed-on: http://review.gluster.org/10581
    Reviewed-by: soumya k <skoduri>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>

Comment 4 Nagaprasad Sathyanarayana 2015-10-25 15:18:32 UTC
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 5 Niels de Vos 2016-06-16 12:53:42 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-3.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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