search for: replica3

I have made a distributed replica3 volume with 6 nodes. I mean this: Volume Name: testvol Type: Distributed-Replicate Volume ID: f271a9bd-6599-43e7-bc69-26695b55d206 Status: Started Snapshot Count: 0 Number of Bricks: 2 x 3 = 6 Transport-type: tcp Bricks: Brick1: 10.0.0.2:/brick Brick2: 10.0.0.3:/brick Brick3: 10.0.0.1:/brick Brick...

...ff quorum. You could then run on the single node until you can save/copy those VM images, preferably by migrating off that volume completely. Create a remote pool using SSHFS if you have nothing else available. THEN I would go back and fix the gluster cluster and migrate back into it. Replica2/Replica3 does not matter if you lose your Gluster network switch, but again the Arb or Rep3 setup makes it easier to recover. I suppose the only advantage of Replica2 is that you can use a cross over cable and not worry about losing the switch, but bonding/teaming works well and there are bonding modes...

...run on the single node until you can > save/copy those VM images, preferably by migrating off that volume > completely. Create a remote pool using SSHFS if you have nothing else > available. THEN I would go back and fix the gluster cluster and > migrate back into it. > > Replica2/Replica3 does not matter if you lose your Gluster network > switch, but again the Arb or Rep3 setup makes it easier to recover. I > suppose the only advantage of Replica2 is that you can use a cross > over cable and not worry about losing the switch, but bonding/teaming > works well and there ar...

Il 25-08-2017 08:32 Gionatan Danti ha scritto: > Hi all, > any other advice from who use (or do not use) Gluster as a replicated > VM backend? > > Thanks. Sorry, I was not seeing messages because I was not subscribed on the list; I read it from the web. So it seems that Pavel and WK have vastly different experience with Gluster. Any plausible cause for that difference? > WK

Il 23-08-2017 18:51 Gionatan Danti ha scritto: > Il 23-08-2017 18:14 Pavel Szalbot ha scritto: >> Hi, after many VM crashes during upgrades of Gluster, losing network >> connectivity on one node etc. I would advise running replica 2 with >> arbiter. > > Hi Pavel, this is bad news :( > So, in your case at least, Gluster was not stable? Something as simple > as an

Hi everyone, I've been using gluster for a few month now, on a simple 2 peers replicated infrastructure, 22Tb each. One of the peers has been offline last week during 10 hours (raid resync after a disk crash), and while my gluster server was healing bricks, I could see some write errors on my gluster clients. I couldn't find a way to isolate my healing peer, in the documentation or