|
Very good, I will give this a try.
Thank you.
Carl
On 2019-07-03 3:56 p.m., John Strunk
wrote:
Nope. Just:
* Ensure all volumes are fully healed so you don't run into
split brain
* Go ahead and shutdown the server needing maintenance
** If you just want gluster down on that sever node: stop
glusterd and kill the glusterfs bricks, then do what you need
to do
** If you just want to power off: then shutdown -h as usual
(don't worry about stopping gluster)
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.
-John
I
have a replica 3 cluster, 3 nodes with bricks and 2 "client"
nodes,
that run the VMs through a mount of the data on the bricks.
Now, one of the bricks need maintenance and I will need to
shut it down
for about 15 minutes.
I didn't find any information on what I am suposed to do.
If I get this right, I am suposed to remove the brick
completely from
the cluster and add them again when the maintenance is
finished ?
Carl
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
