Red Hat Bugzilla – Bug 764216
Default start/stop levels in init.d script are wrong for boot mount
Last modified: 2013-07-24 13:37:01 EDT
The default init script for glusterd says:
# chkconfig: 35 90 12
This makes it start at order 90, and stop at order 12.
At least under RHEL/CentOS and compatible systems it will cause boot problems if we are mounting local node data (or using DNS-RR with only the local node starting), and can also cause shutdown problems as well.
Why is it so:
netfs (network fs mounting script) starts at order 25, and stops at order 75. So at the moment of netfs start/stop local glusterfsd node will not be yet/already available.
We may change init script as following.
# chkconfig: 35 20 80
So the glusterd will start after network (it is at 10/90), but just before netfs.
CHANGE: http://review.gluster.com/746 (In cases of client and server sharing the same machine, mounting GlusterFS at) merged in master by Anand Avati (email@example.com)