Issue

When you stop a running gluster using "service gluster stop" as per instructions under "https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Installation_Guide/chap-Installation_Guide-Register_RHN_1.html" why does it not kill any remaining gluster processes itself rather than depend on the user/administrator to do this?

On my hosts in the gluster cluster which has a geo-replication volume, after having stopped glusterd I have to manually kill off any remaining gluster processes, e.g.

[root@kvm-guest-74 ~]# gluster pe st
Number of Peers: 2

Hostname: shou18lsles09
Uuid: 28789104-e303-426f-9dc5-e05342f33427
State: Peer in Cluster (Disconnected)

Hostname: shou18lsles10
Uuid: 0b823b13-b255-43e4-b7f9-c0838cdf1474
State: Peer in Cluster (Disconnected)

[root@kvm-guest-74 ~]# service glusterd stop
[root@kvm-guest-74 ~]#                                     [  OK  ]

[root@kvm-guest-74 ~]# ps -ef | grep glust
root     13362 13325  0 08:54 pts/0    00:00:00 grep glust
root     26927     1  0  2014 ?        00:04:58 /usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p /var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log -S /var/run/58913699e7ad139a510fd06b094cca36.socket
root     26934     1  0  2014 ?        00:04:57 /usr/sbin/glusterfs -s localhost --volfile-id gluster/glustershd -p /var/lib/glusterd/glustershd/run/glustershd.pid -l /var/log/glusterfs/glustershd.log -S /var/run/caf447e05a287943d4cc7c06ab55bbda.socket --xlator-option *replicate*.node-uuid=3d4f01e2-2896-4da3-8a0b-4522650cae01
[root@kvm-guest-74 ~]# kill 26927 26934
[root@kvm-guest-74 ~]#

Shouldn't the startup/shutdown script should do this for me?