Bug 1309099

Summary:	Cache-invalidation feature state not persistent
Product:	[Community] GlusterFS	Reporter:	Christian Petersen <cpetersen4>
Component:	upcall	Assignee:	Soumya Koduri <skoduri>
Status:	CLOSED EOL	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.7.6	CC:	bugs, cpetersen4, jthottan, skoduri
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-08 10:52:04 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 Christian Petersen 2016-02-16 20:15:43 UTC

Description of problem:  cache-invalidation feature of the cluster is turned off when restarting the gluster cluster


Version-Release number of selected component (if applicable):
3.7.6

How reproducible:  Every time


Steps to Reproduce:
1. stop gluster cluster
2. start gluster cluster
3. type in:  gluster v info

Actual results:
cache-invalidation is set to off

Expected results:
cache-invalidation should still be on

Additional info:
I am using gluster in conjunction with nfs-ganesha

Comment 1 Jiffin 2016-02-23 12:14:07 UTC

Can u check the value for that option in /var/lib/glusterd/vols/<vol name>/info before and restarting the cluster?

Comment 2 Kaushal 2017-03-08 10:52:04 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.

Comment 3 Christian Petersen 2018-12-03 20:50:48 UTC

This version of software is no longer in use and I am no longer responsible for it's implementation.