summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPrasanna Kumar Kalever <prasanna.kalever@redhat.com>2016-08-17 17:47:08 +0530
committerAtin Mukherjee <amukherj@redhat.com>2016-08-29 04:55:15 -0700
commit87303b77ddbdc29a415acc2c73bfaafa9be10609 (patch)
tree606bf5eaf02effd78e32df59b8bb814224c9f1c2
parent14b46be09c98c1ef75f55af34ec762b3e34899f1 (diff)
extras: kill gsyncd before glusterfsd
It's a good practice to kill gsyncd before brick process, else we see unnecessary loops and logs of bring up the faulty bricks Change-Id: I2d2176f2bf5014f3afd622194a8b2d60c86926af BUG: 1367771 Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com> Reviewed-on: http://review.gluster.org/15187 Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com> CentOS-regression: Gluster Build System <jenkins@build.gluster.org> Smoke: Gluster Build System <jenkins@build.gluster.org> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> Reviewed-by: Atin Mukherjee <amukherj@redhat.com> Reviewed-by: Kotresh HR <khiremat@redhat.com>
-rwxr-xr-xextras/stop-all-gluster-processes.sh4
1 files changed, 2 insertions, 2 deletions
diff --git a/extras/stop-all-gluster-processes.sh b/extras/stop-all-gluster-processes.sh
index f11c634007c..69fd601273e 100755
--- a/extras/stop-all-gluster-processes.sh
+++ b/extras/stop-all-gluster-processes.sh
@@ -176,16 +176,16 @@ main()
shift $((OPTIND-1))
kill_mounts TERM
- kill_bricks_and_services TERM
kill_georep_gsync TERM
+ kill_bricks_and_services TERM
sleep 5;
echo ""
# still not Terminated? let's pass SIGKILL
kill_mounts KILL
- kill_bricks_and_services KILL
kill_georep_gsync KILL
+ kill_bricks_and_services KILL
exit ${errors};
}