Diego Zuccato
2021-Feb-03 13:03 UTC
[Gluster-users] Proper procedure to reduce an active volume
Hello all. What is the proper procedure to reduce a "replica 3 arbiter 1" volume? The procedure I've found is: 1) # gluster volume remove-brick VOLNAME BRICK start (repeat for each brick to be removed, but being a r3a1 should I remove both bricks and the arbiter in a single command or multiple ones?) 2) # gluster volume remove-brick VOLNAME BRICK status (to monitor migration) 3) # gluster volume remove-brick VOLNAME BRICK commit (to finalize the removal) 4) umount and reformat the freed (now unused) bricks Is this safe? And once the bricks are removed I'll have to distribute arbiters across the current two data servers and a new one (currently I'm using a dedicated VM just for the arbiters). But that's another pie :) -- Diego Zuccato DIFA - Dip. di Fisica e Astronomia Servizi Informatici Alma Mater Studiorum - Universit? di Bologna V.le Berti-Pichat 6/2 - 40127 Bologna - Italy tel.: +39 051 20 95786
Strahil Nikolov
2021-Feb-03 17:15 UTC
[Gluster-users] Proper procedure to reduce an active volume
Replica volumes do not require the 'start + commit' - it's needed only for distributed replicated volumes and other types of volumes. Yet, I'm not sure if removing a data brick (and keeping the arbiter) makes any sense. Usually, I just remove 1 data copy + the arbiter to? reshape the volume. Keep in mind that as you remove a brick you need to specify the new replica count.For example you have 'replica 3 arbiter 1' and you want to remove the second copy and the arbiter:gluster volume remove-brick <VOLUME> replica 1 server2:/path/to/brick arbiter:/path/to/brick force If you wish to reuse block devices, don't forget to rebuild the FS (as it's fastest way to cleanup)!When you increase the count (add second data brick and maybe arbiter), you should run:gluster volume add-brick <VOLUME> replica 3 arbiter 1 server4:/path/to/brick arbiter2:/path/to/brick gluster volume heal <VOLUME> full Best Regards,Strahil Nikolov Sent from Yahoo Mail on Android On Wed, Feb 3, 2021 at 15:03, Diego Zuccato<diego.zuccato at unibo.it> wrote: Hello all. What is the proper procedure to reduce a "replica 3 arbiter 1" volume? The procedure I've found is: 1) # gluster volume remove-brick VOLNAME BRICK start (repeat for each brick to be removed, but being a r3a1 should I remove both bricks and the arbiter in a single command or multiple ones?) 2) # gluster volume remove-brick VOLNAME BRICK status (to monitor migration) 3) # gluster volume remove-brick VOLNAME BRICK commit (to finalize the removal) 4) umount and reformat the freed (now unused) bricks Is this safe? And once the bricks are removed I'll have to distribute arbiters across the current two data servers and a new one (currently I'm using a dedicated VM just for the arbiters). But that's another pie :) -- Diego Zuccato DIFA - Dip. di Fisica e Astronomia Servizi Informatici Alma Mater Studiorum - Universit? di Bologna V.le Berti-Pichat 6/2 - 40127 Bologna - Italy tel.: +39 051 20 95786 ________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users at gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20210203/6c45d9e8/attachment.html>
Nag Pavan Chilakam
2021-Feb-04 18:28 UTC
[Gluster-users] Proper procedure to reduce an active volume
On Wed, 3 Feb 2021, 18:33 Diego Zuccato, <diego.zuccato at unibo.it> wrote:> Hello all. > > What is the proper procedure to reduce a "replica 3 arbiter 1" volume? >Can you kindly elaborate the volume configuration. Is this a plain arbiter volume or is it a distributed arbiter volume? Please share the volume info so that we can help you better> The procedure I've found is: > 1) # gluster volume remove-brick VOLNAME BRICK start > (repeat for each brick to be removed, but being a r3a1 should I remove > both bricks and the arbiter in a single command or multiple ones?) >No , you can mention bricks of a distributed subvolume in one command. If you are having a 1x(2+1a) volume , then you should mention only one brick. Start by removing the arbiter brick> 2) # gluster volume remove-brick VOLNAME BRICK status > (to monitor migration) > 3) # gluster volume remove-brick VOLNAME BRICK commit > (to finalize the removal) > 4) umount and reformat the freed (now unused) bricks > Is this safe?What is the actual need to remove bricks? If you feel this volume is not needed anymore , then just delete the volume, instead of going through each brick deletion> > And once the bricks are removed I'll have to distribute arbiters across > the current two data servers and a new one (currently I'm using a > dedicated VM just for the arbiters). But that's another pie :) > > -- > Diego Zuccato > DIFA - Dip. di Fisica e Astronomia > Servizi Informatici > Alma Mater Studiorum - Universit? di Bologna > V.le Berti-Pichat 6/2 - 40127 Bologna - Italy > tel.: +39 051 20 95786 > ________ > > > > Community Meeting Calendar: > > Schedule - > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC > Bridge: https://meet.google.com/cpu-eiue-hvk > Gluster-users mailing list > Gluster-users at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20210204/ff829ecf/attachment.html>