[ovirt-users] oVirt over gluster: Replacing a dead host

Hello all, I'm attempting to replace a dead host in a replica 2 + arbiter gluster setup and replace it with a new host. I've already set up a new host (same hostname..localdomain) and got into the cluster. $ gluster peer status Number of Peers: 2 Hostname: office-wx-hv3-lab-gfs Uuid: 4e13f796-b818-4e07-8523-d84eb0faa4f9 State: Peer in Cluster (Connected) Hostname: office-wx-hv1-lab-gfs.localdomain <------ This is a new host. Uuid: eee17c74-0d93-4f92-b81d-87f6b9c2204d State: Peer in Cluster (Connected) $ gluster volume info GV2Data Volume Name: GV2Data Type: Replicate Volume ID: c1946fc2-ed94-4b9f-9da3-f0f1ee90f303 Status: Stopped Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick <------ This is the dead host. Brick2: office-wx-hv2-lab-gfs:/mnt/LogGFSData/brick Brick3: office-wx-hv3-lab-gfs:/mnt/LogGFSData/brick (arbiter) ... Looking at the docs, it seems that I need to remove the dead brick. $ gluster volume remove-brick GV2Data office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick start Running remove-brick with cluster.force-migration enabled can result in data corruption. It is safer to disable this option so that files that receive writes during migration are not migrated. Files that are not migrated can then be manually copied after the remove-brick commit operation. Do you want to continue with your current cluster.force-migration settings? (y/n) y volume remove-brick start: failed: Removing bricks from replicate configuration is not allowed without reducing replica count explicitly So I guess I need to drop from replica 2 + arbiter to replica 1 + arbiter (?). $ gluster volume remove-brick GV2Data replica 1 office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick start Running remove-brick with cluster.force-migration enabled can result in data corruption. It is safer to disable this option so that files that receive writes during migration are not migrated. Files that are not migrated can then be manually copied after the remove-brick commit operation. Do you want to continue with your current cluster.force-migration settings? (y/n) y volume remove-brick start: failed: need 2(xN) bricks for reducing replica count of the volume from 3 to 1 ... What am I missing? - Gilboa