Description of problem: ----------------------- Fails to set group virt option on distribute volume type since some of the options are specific to replica volume types. Version-Release number of selected component (if applicable): -------------------------------------------------------------- RHGS 3.4 Batch Update1 How reproducible: ------------------ Always Steps to Reproduce: -------------------- 1. Create a distribute volume and select optimize for virt store Actual result: -------------- Fails to set all volume options on the distribute volume Expected result: ---------------- Create a separate virt profile with volume options applicable for distributed volume
Krutika - I'm assigning this to you. Seems straight forward.
(In reply to Atin Mukherjee from comment #1) > Krutika - I'm assigning this to you. Seems straight forward. Indeed it is! But even before that, do you mind responding to https://bugzilla.redhat.com/show_bug.cgi?id=1638674#c6 ? -Krutika
Response has been captured at the RHHI BZ.
upstream patch : https://review.gluster.org/#/c/glusterfs/+/21735/
RHGS-specific patch posted downstream - https://code.engineering.redhat.com/gerrit/#/c/158487
Tested with glusterfs-3.12.2-35.el7rhgs. Optimizing the distributed volume for virt store case is made possible using 'distributed-virt' profile [root@ ~]# gluster volume set dvol group distributed-virt volume set: success [root@ ~]# gluster volume info dvol Volume Name: dvol Type: Distribute Volume ID: 78168ec8-1abe-4f9a-a3dd-a1b76414fac3 Status: Created Snapshot Count: 0 Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: host1.redhat.com:/tmp/1 Options Reconfigured: performance.client-io-threads: on server.event-threads: 4 client.event-threads: 4 user.cifs: off features.shard: on network.remote-dio: enable performance.low-prio-threads: 32 performance.io-cache: off performance.read-ahead: off performance.quick-read: off transport.address-family: inet nfs.disable: on
The doc text has been updated. Kindly review the technical accuracy.
(In reply to Srijita Mukherjee from comment #12) > The doc text has been updated. Kindly review the technical accuracy. Looks good to me.
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-2019:0263