Bug 1445251
Summary: | [Parallel Readdir] : Unable to re-enable parallel readdir after disabling it if rda cache limit is > 1GB | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Ambarish <asoman> |
Component: | glusterfs | Assignee: | Poornima G <pgurusid> |
Status: | CLOSED ERRATA | QA Contact: | Ambarish <asoman> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.3 | CC: | amukherj, bturner, rhinduja, rhs-bugs, skoduri, vbellur |
Target Milestone: | --- | ||
Target Release: | RHGS 3.3.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.8.4-26 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-09-21 04:39:40 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: | 1438245 | ||
Bug Blocks: | 1417151 |
Description
Ambarish
2017-04-25 10:58:55 UTC
When parallel readdir is enabled, the cache limit is (dist count * 1GB). Lets say the cache limit was set to 2 GB and then parallel readdir was disabled, the validation of rda-cache-limit fails, as the rda instance is only one(without parallel readdir) and the cache limit is set to 2GB more than the limit(1GB). Thus, mount or any other volume set etc will fail. upstream patch : https://review.gluster.org/#/c/17338/ downstream patch : https://code.engineering.redhat.com/gerrit/#/c/106815/ Verified on 3.8.4-27. I am able to disable parallel readdir and access FUSE mounts from multiple clients. 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/RHBA-2017:2774 |