Hi,
You had server-quorum enabled which could be the cause of the errors
you were getting at the first place. In latest releases only
client-quorum is enabled and the server-quorum is disabled by default.
Yes, the order matters in such cases.
Regards,
Karthik
On Fri, Aug 28, 2020 at 2:37 AM WK
So success!
I dont know why but when I set "server-quorum-type" to none FIRST it
seemed to work without complaining about quorum.
then quorum-type was able to be set to none as well
gluster volume set VOL cluster.server-quorum-type none
gluster volume set VOL cluster.quorum-type none
No Luck. Same problem.
I stopped the volume.
I ran the remove-brick command. It warned about not being able to
migrate files from removed bricks and asked if I want to continue.
when I say 'yes'
Gluster responds with 'failed: Quorum not met Volume operation not allowed'
-wk
On 8/26/2020
Sadly I have no idea why rebalance did that , so you should check the logs on
all nodes for clues.
Is there any reason why you used "force" in that command ?
Best Regards,
Strahil Nikolov
В четвъртък, 27 август 2020 г., 17:32:24 Гринуич+3, Pat Haley
написа:
Hi,
We have
Hi there
I wonder if eager lock for a 2-node gluster brings some improvement
specially in this new gluster 8.1...
Is there any pros?
Thanks
---
Gilberto Nunes Ferreira
Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge:
Hi,
The Gluster community is pleased to announce the release of Gluster8.1
(packages available at [1]).
Release notes for the release can be found at [2].
Major changes, features, improvements and limitations addressed in this
release:
- Performance improvement over the creation of large files
When a file should be moved based on its dht hash mapping but the target that
it should be moved to has less free space than the origin, the rebalance
command does not move the file and leaves the dht pointer in place. When you
use "force", you override that behavior and always move each file
Hi Strahil
The documentation I looked at:
*
https://docs.google.com/document/d/18iGX6I7I0yHUZ1zAfLIEnXDRPkIoMh6CHmwyyb6J4GM/edit#heading=h.oogvisuwd2qd
suggested that not using force might leave some links behind that could
affect performance
Thanks
Pat
On 8/27/20 10:43 AM, Strahil
Hi,
We have distributed gluster volume spread across 4 bricks. Yesterday I
noticed that the remaining space was uneven (about 2.7TB, 1.7TB, 1TB,
1TB) so I issued the following rebalance command
* |gluster volume rebalance start force|
Today I see that instead, things have gotten even
