Description of problem: For one of the VM store use-cases, we want to start with a single node gluster volume and then later change to replica 3 gluster volume for redundancy. This operation should be supported, and the heal should happen automatically when user sets a replica count and adds the additional bricks. How reproducible: NA
T
No, it should work fine, especially since https://bugzilla.redhat.com/show_bug.cgi?id=1276203 has been fixed.
Realised that there is a corner case: BZ 1400092
Update: ========= > tried below scenario 1) create 1 * 1 volume on a single node 2) create different IO which consists of
Update : ============ > Covered below scenarios as well. Scenario 1: converting 1 * 1 to 1 * 3 Steps: 1) create 1 * 1 distribute volume and start 2) create files and dirs from client ( 13k files and 13k dirs ) 3) add bricks to volume so that it will convert to 1 * 3 ( Replicate ) 4) Monitor the heal completion. 5) arequal-checksum is same on all the bricks and equals to arequal-checksum of client mountpoint Scenario 1: converting 2 * 1 to 2 * 3 1) create 2 * 1 distribute volume and start 2) create files and dirs from client ( 13k files and 13k dirs ) 3) add bricks to volume so that it will convert to 2 * 3 ( Distributed-Replicate ) 4) Monitor the heal completion. 5) arequal-checksum is same on all the bricks in the replica set Changing status to Verified.
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/RHSA-2018:2607