Bug 1309099 - Cache-invalidation feature state not persistent
Summary: Cache-invalidation feature state not persistent
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: upcall
Version: 3.7.6
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Soumya Koduri
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-16 20:15 UTC by Christian Petersen
Modified: 2018-12-03 20:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-08 10:52:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


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