Bug 1697820
| Summary: | rhgs 3.5 server not compatible with 3.4 client | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sweta Anandpara <sanandpa> |
| Component: | glusterd | Assignee: | Sanju <srakonde> |
| Status: | CLOSED ERRATA | QA Contact: | Kshithij Iyer <kiyer> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.5 | CC: | amukherj, kiyer, nchilaka, pasik, rhs-bugs, sheggodu, srakonde, storage-qa-internal, vbellur |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-6.0-2 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-30 12:20:50 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: | 1697907, 1698042, 1698471 | ||
| Bug Blocks: | 1696807 | ||
|
Description
Sweta Anandpara
2019-04-09 07:39:59 UTC
There're two parts to this problem. What you have hit is explained in (1), but if we fix only (1) you would end up hitting (2) , so we need to fix both. The root cause is self explanatory from the commit messages but I'll paste here too 1. upstream patch : https://review.gluster.org/#/c/22539/ (we still need to get an agreement on this approach) 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. The proposed fix here is to rename the key in quick-read to 'quick-read-cache-invalidation' so that both these features have distinct identification. While this brings in by itself a backward compatibility challenge where this feature is enabled in an existing cluster and when the same is upgraded to a version where this change exists, it will lead to an unidentified old key. But as a workaround we can always ask users upgrading to release-7 version to turn off this option, upgrade the cluster and turn it back on with the new key. This needs to be documented once the patch is accepted. 2. upstream patch : https://review.gluster.org/22536 Considering ctime is a client side feature, we can't blindly load ctime xlator into the client graph if it's explicitly turned off, that'd result into backward compatibility issue where an old client can't mount a volume configured on a server which is having ctime feature. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:3249 |