remove-brick replica 1 will deconfigure your Arbiter which leads to brick prep
work on the Arbiter - just more efforts.
>Also, you suggested creating a fresh logical volume on the node where I'm
>converting from full replica to arbiter.Would it not suffice to simply go in
>and erase all of the d
Thank you.
I'm doing some more research & reading on this to make sure I understand
everything before I do this work.
You wrote:
> If you rebuild the raid, you are destroying the brick, so after mounting it
> back, you will need to reset-brick. If it doesn't work for some reason , you
> can alw
>2a) remove-brick replica 2
-- if I understand correctly, this will basically just reconfigure the existing
volume to replicate between the 2 bricks, and not all 3 ... is this correct?
Yep, you are kicking out the 3rd node and the volume is converted to replica 2.
Most probably the command would
HI Jayme & Strahil,
Thank you again for your messages.
Reading
https://stackoverflow.com/questions/52394849/can-i-change-glusterfs-replica-3-to-replica-3-with-arbiter-1,
I think I understand now what Strahil is suggesting.
It sounds to me like you're saying I can reconfigure the existing gluste
Just a thought but depending on resources you might be able to use your 4th
server as nfs storage and live migrate vm disks to it and off of your
gluster volumes. I’ve done this in the past when doing major maintenance on
gluster volumes to err on the side of caution.
On Sat, Jul 10, 2021 at 7:22
Hmm right as I said that, I just had a thought.
I DO have a "backup" server in place (that I haven't even started using yet),
that currently has some empty hard drive bays.
It would take some extra work, but I could use that 4th backup server as a
temporary staging ground to begin building t
Thank you. And yes, I agree, this needs to occur in a maintenance window and be
done very carefully. :)
My only problem with this method is that I need to *replace* disks in the two
servers.
I don't have any empty hard drive bays, so will effectively need to put a host
into maintenance mode, re
Hi David,
any storage operation can cause unexpected situations, so always plan your
activites for low traffic hours and test them on your test environment in
advance.
I think it's easier if you (command line):
-verify no heals are pending. Not a single one.- set the host to maintenance
over ov
8 matches
Mail list logo
