You already mentioned that regular arbiter works fine for you .
What are the considerations to switch from regular to thin arbiter ?
I think that thin arbiter is suitable for environments where a third node is
not possible locally and is a compromise in order to avoid 'replica 2' volumes.
well, that is why I was asking.
Yes, we are extremely satisfied with the existing arbiter. It makes a
measurable difference vs true Replica 3.
I was curious as to if Thin Arbiter was an *improvement* over regular
Arbiter or even considered the new 'Arbiter' going forward.
The documentation
OK, so it seems 8.x is the way to go
So what about Thin Arbiter?
Is anyone one using it in production?
-wk
On 12/18/2020 12:59 AM, Olaf Buitelaar wrote:
It is in their release notes;
https://docs.gluster.org/en/latest/release-notes/7.9/
