<div><br><div class="gmail_quote"><div>On Sun, 11 Jun 2017 at 16:03, Lindsay Mathieson <<a href="mailto:lindsay.mathieson@gmail.com">lindsay.mathieson@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 11/06/2017 6:42 PM, Atin Mukherjee wrote:<br>
> If the dead server doesn't host any volumes (bricks of volumes to be<br>
> specific) then you can actually remove the uuid entry from<br>
> /var/lib/glusterd from other nodes and restart glusterd instances one<br>
> after another as a workaround.<br>
<br>
The server hosted a brick, but I removed that after it died with<br>
"gluster v remove-brick force". Does that mean I could edit glusterd as<br>
you suggest?</blockquote><div><br></div><div>Yes</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
<br>
> With Glusterd2, we will see if we can have a better user experience here.<br>
<br>
<br>
That would be good - I imagine in a lot of cases the only way a server<br>
is removed is *after* it has died.<br>
<br>
<br>
Thanks.<br>
<br>
<br>
--<br>
Lindsay Mathieson<br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature">--Atin</div>