[Gluster-users] Upgrade from 6.9 to 7.7 stuck (peer is rejected)
hunter86_bg at yahoo.com
Mon Oct 26 17:06:37 UTC 2020
Detaching the arbiter is pointless...
Quota is an extended file attribute, and thus disabling and reenabling quota on a volume with millions of files will take a lot of time and lots of IOPS. I would leave it as a last resort.
Also, it was mentioned in the list about the following script that might help you:
You can take a look in the mailing list for usage and more details.
В понеделник, 26 октомври 2020 г., 16:40:06 Гринуич+2, Diego Zuccato <diego.zuccato at unibo.it> написа:
Il 26/10/20 15:09, mabi ha scritto:
> Right, seen liked that this sounds reasonable. Do you actually remember the exact command you ran in order to remove the brick? I was thinking this should be it:
> gluster volume remove-brick <VOLNAME> <BRICK> force
> but should I use "force" or "start"?
Memory does not serve me well (there are 28 disks, not 26!), but bash
history does :)
# gluster volume remove-brick BigVol replica 2
# gluster peer detach str957-biostq
# gluster peer probe str957-biostq
# gluster volume add-brick BigVol replica 3 arbiter 1
You obviously have to wait for remove-brick to complete before detaching
>> IIRC it took about 3 days, but the arbiters are on a VM (8CPU, 8GB RAM)
>> that uses an iSCSI disk. More than 80% continuous load on both CPUs and RAM.
> That's quite long I must say and I am in the same case as you, my arbiter is a VM.
Give all the CPU and RAM you can. Less than 8GB RAM is asking for
troubles (in my case).
DIFA - Dip. di Fisica e Astronomia
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
Community Meeting Calendar:
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Gluster-users mailing list
Gluster-users at gluster.org
More information about the Gluster-users