Should be OK. But running the same version on both clients and servers is
always the safest bet.
-Krutika
On Mon, Aug 22, 2016 at 10:39 AM, qingwei wei wrote:
> Hi,
>
> I updated my client to 3.7.14 and i no longer experience split-brain
> error. It seems like there is some changes on the clien
Hi,
I updated my client to 3.7.14 and i no longer experience split-brain
error. It seems like there is some changes on the client side that fix
this error. Please note that, for this test, i still stick to 3.7.10
server. Will it be an issue with client and server using different
version?
Cw
On T
3.7.11 had quite a few bugs in afr and sharding+afr interop that were fixed
in 3.7.12.
Some of them were about files being reported as being in split-brain.
Chances are that some of them existed in 3.7.10 as well - which is what
you're using.
Do you mind trying the same test with 3.7.12 or a later
Hi Niels,
My situation is that when i unplug the HDD physically, the FIO
application exits with Input/Output error. However, when i do echo
offline on the disk, the FIO application does freeze a bit but still
manage to resume the IO workload after the freeze.
>From what i can see from the client
On Tue, Aug 16, 2016 at 01:34:36PM +0800, qingwei wei wrote:
> Hi,
>
> I am currently trying to test the distributed replica (3 replicas)
> reliability when 1 brick is down. I tried using both software unplug
> method by issuing the exho offline > /sys/block/sdx/device/state and
> also physically
Hi,
I am currently trying to test the distributed replica (3 replicas)
reliability when 1 brick is down. I tried using both software unplug
method by issuing the exho offline > /sys/block/sdx/device/state and
also physically unplug the HDD and i encountered 2 different outcomes.
For software unplu
