On Mon, 9 May 2011 at 10:33am, Vikas Gorur wrote
>> I think the question is why there's a single init.d script that starts or
>> shuts down both daemon and client at once.
>
> The init.d/glusterd script has nothing whatsoever to do with the client.
> It only controls starting/stopping the server. The client is an
> independent process that is started by mounting and stopped by
> unmounting.
In theory that's how it should work. In practice, it isn't. Just look at
the script itself:
stop()
{
echo -n $"Stopping $BASE:"
killproc $BASE
echo
pidof -c -o %PPID -x $GLUSTERFSD &> /dev/null
[ $? -eq 0 ] && killproc $GLUSTERFSD &> /dev/null
pidof -c -o %PPID -x $GLUSTERFS &> /dev/null
[ $? -eq 0 ] && killproc $GLUSTERFS &> /dev/null
}
So it kills the glusterd ($BASE), glusterfsd, *and* glusterfs processes.
That last one unmounts any mounted gluster filesystems. If one wanted to,
e.g., shut down one server node of a replicated pair *but* still access
the glusterfs mount from that node, one would have to remount the FS after
doing a "service glusterd stop".
--
Joshua Baker-LePain
QB3 Shared Cluster Sysadmin
UCSF
