Bug 1663102
| Summary: | Change default value for client side heal to off for replicate volumes | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Sunil Kumar Acharya <sheggodu> |
| Component: | replicate | Assignee: | Sunil Kumar Acharya <sheggodu> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | mainline | CC: | bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-6.0 | Doc Type: | Release Note |
| Doc Text: |
Performance degrades significantly on AFR volumes under certain circumstances due to client-side healing. In order to provide consistency in performance, this change disables client side heal for AFR volumes by updating default value for client-side heal to "off". Users have to explicitly set it to "on" if they need client-side heal for AFR volumes.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-02-05 17:48:01 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
Sunil Kumar Acharya
2019-01-03 07:28:42 UTC
REVIEW: https://review.gluster.org/21938 (cluster/afr: Disable client side heals in AFR by default.) posted (#6) for review on master by Sunil Kumar Acharya REVIEW: https://review.gluster.org/21938 (cluster/afr: Disable client side heals in AFR by default.) posted (#8) for review on master by Ravishankar N REVIEW: https://review.gluster.org/22051 (cluster/afr: Change data-self-heal option to bool) posted (#1) for review on master by None REVIEW: https://review.gluster.org/22052 (cluster/afr: Change data-self-heal option to bool) posted (#1) for review on master by None This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/ |