<div dir="ltr">Nope. Just:<div>* Ensure all volumes are fully healed so you don't run into split brain</div><div>* Go ahead and shutdown the server needing maintenance</div><div>** If you just want gluster down on that sever node: stop glusterd and kill the glusterfs bricks, then do what you need to do</div><div>** If you just want to power off: then shutdown -h as usual (don't worry about stopping gluster)</div><div><br></div><div>When you bring the server back up, glusterd and the bricks should start, and the bricks should heal from the 2 replicas that remained up during maintenance.</div><div><br></div><div>-John</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 3, 2019 at 3:48 PM Carl Sirotic <<a href="mailto:csirotic@evoqarchitecture.com">csirotic@evoqarchitecture.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I have a replica 3 cluster, 3 nodes with bricks and 2 "client" nodes, <br>
that run the VMs through a mount of the data on the bricks.<br>
<br>
Now, one of the bricks need maintenance and I will need to shut it down <br>
for about 15 minutes.<br>
<br>
I didn't find any information on what I am suposed to do.<br>
<br>
If I get this right, I am suposed to remove the brick completely from <br>
the cluster and add them again when the maintenance is finished ?<br>
<br>
<br>
Carl<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="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div>