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