<html><head></head><body><div>All,</div><div><br></div><div>I added a third peer for a arbiter brick host to replica 2 cluster. Then I realized I can't use it since it has no infiniband like the other two hosts (infiniband and ethernet for clients). So I removed the new arbiter bricks from all of the volumes. However, I can't detach the peer as it keeps saying there are bricks it hosts. Nothing in volume status or info shows that host to be involved.</div><div><br></div><div>gluster peer detach innuendo force</div><div>peer detach: failed: Brick(s) with the peer innuendo exist in cluster</div><div></div><div><span><pre><br></pre><pre>The Self-heal daemon is still running on innuendo for each brick.</pre><pre><br></pre><pre>Should I re-add the arbiter brick and wait for the arbiter heal process to complete? How do I take the arbiter brick out and not break things? It was added using:</pre><pre>for fac in <list of volumes>; do gluster volume add-brick ${fac}2 replica 3 arbiter 1 innuendo:/data/glusterfs/${fac}2/brick; done</pre><pre><br></pre><pre>And then removed using:</pre><pre>for fac in <list of volumes>; do gluster volume remove-brick ${fac}2 replica 2 innuendo:/data/glusterfs/${fac}2/brick force; done</pre><pre><br></pre><pre><br></pre><pre>Adding a new 3rd full brick host soon to avoid split-brain and trying to get this cleaned up before the new hardware arrives and I start the sync.</pre><pre>-- <br></pre><pre>James P. Kinney III
Every time you stop a school, you will have to build a jail. What you
gain at one end you lose at the other. It's like feeding a dog on his
own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain
http://heretothereideas.blogspot.com/
</pre></span></div></body></html>