Bug 1218858

Summary:	nfs-ganesha: Multi-head nfs need Upcall Cache invalidation support
Product:	[Community] GlusterFS	Reporter:	Meghana <mmadhusu>
Component:	ganesha-nfs	Assignee:	Meghana <mmadhusu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	skoduri, vagarwal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1213752	Environment:
Last Closed:	2015-05-14 17:29:37 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:
Bug Depends On:	1213752
Bug Blocks:	1199352

Description Meghana 2015-05-06 04:57:30 UTC

+++ This bug was initially created as a clone of Bug #1213752 +++

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.

--- Additional comment from Anand Avati on 2015-05-05 08:59:40 EDT ---

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)

--- Additional comment from Anand Avati on 2015-05-05 15:47:05 EDT ---

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 1 Anand Avati 2015-05-06 05:00:30 UTC

REVIEW: http://review.gluster.org/10594 (Cache-invalidation : set to on/off depending on ganesha.enable value) posted (#1) for review on release-3.7 by Meghana M (mmadhusu)

Comment 2 Anand Avati 2015-05-07 08:47:18 UTC

COMMIT: http://review.gluster.org/10594 committed in release-3.7 by Niels de Vos (ndevos) 
------
commit 6d82215ab95d95ace13465a3efd384e50942ea67
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'
    
    This is a back-port of the fix that is merged on master.
    http://review.gluster.org/#/c/10581/
    
    Change-Id: I1b24c88b5a7cce963a184a0a90cee839873a8d6b
    BUG: 1218858
    Signed-off-by: Meghana Madhusudhan <mmadhusu>
    Reviewed-on: http://review.gluster.org/10594
    Reviewed-by: jiffin tony Thottan <jthottan>
    Reviewed-by: soumya k <skoduri>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaleb KEITHLEY <kkeithle>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Niels de Vos <ndevos>

Comment 3 Niels de Vos 2015-05-14 17:29:37 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Niels de Vos 2015-05-14 17:36:00 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:38:22 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:47:22 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user