| Summary: | AFR : "read-subvolume" volume option can be used only on pure replicate volumes. | ||
|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | spandura |
| Component: | replicate | Assignee: | Bug Updates Notification Mailing List <rhs-bugs> |
| Status: | CLOSED EOL | QA Contact: | storage-qa-internal <storage-qa-internal> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.1 | CC: | rhs-bugs, storage-qa-internal, vbellur |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-03 17:19:44 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: | |
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/ If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release. |
Description of problem: ======================= On a distribute-replicate volume set "read-subvolume" volume option to a brick from one of the replicate subvolumes. The same value is applied to rest of the subvolumes also. Option: cluster.read-subvolume Default Value: (null) Description: inode-read fops happen only on one of the bricks in replicate. Afr will prefer the one specified using this option if it is not stale. Option value must be one of the xlator names of the children. Ex: <volname>-client-0 till <volname>-client-<number-of-bricks - 1> Expected result:- ===================== "read-subvolume" volume option should be sub-volume level not for the entire volume root@rhs-client11 [Nov-25-2013-10:38:32] >gluster v info vol2 Volume Name: vol2 Type: Distributed-Replicate Volume ID: 459988a6-ae4d-4ac2-ac7d-31282ef446f7 Status: Created Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: rhs-client11:/rhs/bricks/vol2-b1 Brick2: rhs-client12:/rhs/bricks/vol2-b1-rep Brick3: rhs-client11:/rhs/bricks/vol2-b2 Brick4: rhs-client12:/rhs/bricks/vol2-b2-rep Options Reconfigured: cluster.read-subvolume: vol2-client-0 Fuse vol file contents: ======================== volume vol2-replicate-0 type cluster/replicate option read-subvolume vol2-client-0 subvolumes vol2-client-0 vol2-client-1 end-volume volume vol2-replicate-1 type cluster/replicate option read-subvolume vol2-client-0 subvolumes vol2-client-2 vol2-client-3 end-volume Here "vol2-client-0" brick is not applicable for "vol2-replicate-1" subvolume. Version-Release number of selected component (if applicable): ============================================================== glusterfs 3.4.0.43.1u2rhs built on Nov 12 2013 07:38:20