|
Setting up a pacemaker/glusterfs cluster I noticed that the
ocf:glusterfs:volume agent only shuts down the bricks in the
specified volume when the resource is disabled but does not shut
down the shd. The problem was actually referenced in redhat
bugzilla 1233333:
https://bugzilla.redhat.com/show_bug.cgi?id=1233333
but there was no resolution there and I couldn't find anything
else describing the issue. I'm running gluster 3.10.1:
# glusterfs -V
glusterfs 3.10.1
Repository revision: git://git.gluster.org/glusterfs.git
Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
It is licensed to you under your choice of the GNU Lesser
General Public License, version 3 or any later version (LGPLv3
or later), or the GNU General Public License, version 2 (GPLv2),
in all cases as published by the Free Software Foundation.
gluster volume status shows all bricks are offline; only the shd
(on both nodes) is running.
So the question is, does the running shd cause any problems? I.E.,
if I put one of the nodes in the cluster on standby, shutting down
the brick PIDs and the glusterd but leaving the shd, will that
cause any issues down the road? Or should I manually execute
gluster volume <volname> stop each time to ensure all is
clean?
TIA,
Dan
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
