Red Hat Bugzilla – Bug 815483
extras/init.d/glusterd-Redhat stop action kills glusterfsd?
Last modified: 2013-12-18 19:08:04 EST
Description of problem:
There are three initscripts in extras/init.d, debian, suse, and redhat. of these, the debian & suse scripts "stop" action only stops the glusterd process, and does not touch running glusterfsd processes. the redhat script (line 52-53), on the other hand, appears to stop both glusterd & glusterfsd processes. Is that right?
Version-Release number of selected component (if applicable):
Personally, I can only confirm the behavior on debian-derived distros (debian & ubuntu) and it is true that "service glusterd stop" does not kill running glusterfsd processes.
I do not have access to a redhat or suse box to test.
Steps to Reproduce:
1. Create volume
2. Start volume
3. "service glusterd stop"
4. did the glusterfsd process get killed also?
On debian/ubuntu only the glusterd process is killed, glusterfsd processes are left alone.
The expected behavior is that only the glusterd process will be killed by "service glusterd stop", but glusterfsd processes will be left alone.
IMHO there needs to be consensus & consistency across distributions as to what "service glusterd stop" will accomplish. I think it should only stop glusterd, and leave running glusterfsd processes alone, because those are controlled pool-wide using "gluster volume start/stop" commands.
patch @ http://review.gluster.com/2919 fixes the issue. This will go in after a review.
Patch committed in upstream.
Verified in master (f2a3291c2fe5a00bca1e4a77a37560ec30cc24bf)