Bug 1698042

Summary: quick-read cache invalidation feature has the same key of md-cache
Product: [Community] GlusterFS Reporter: Atin Mukherjee <amukherj>
Component: quick-readAssignee: bugs <bugs>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, nchilaka
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-08 05:10:39 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:
Bug Depends On:    
Bug Blocks: 1697820    

Description Atin Mukherjee 2019-04-09 13:41:04 UTC
Description of problem:

    With group-metadata-cache group profile settings
    performance.cache-invalidation option when turned on enables both md-cache
    and quick-read xlator's cache-invalidation feature. While the intent of
    the group-metadata-cache is to set md-cache xlator's cache-invalidation
    feature, quick-read xlator also gets affected due to the same. While
    md-cache feature and it's profile existed since release-3.9,
    quick-read cache-invalidation was introduced in release-4 and due to
    this op-version mismatch on any cluster which is >= glusterfs-4 when
    this group profile is applied it breaks backward compatibility with the
    old clients.

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

Comment 1 Worker Ant 2019-04-09 13:48:26 UTC
REVIEW: https://review.gluster.org/22539 (quick-read: rename cache-invalidation key to avoid redundant keys) posted (#1) for review on master by Atin Mukherjee

Comment 2 Worker Ant 2019-07-08 05:10:39 UTC
REVIEW: https://review.gluster.org/22539 (quick-read: rename cache-invalidation key to avoid redundant keys) merged (#6) on master by Raghavendra G