From 87303b77ddbdc29a415acc2c73bfaafa9be10609 Mon Sep 17 00:00:00 2001 From: Prasanna Kumar Kalever Date: Wed, 17 Aug 2016 17:47:08 +0530 Subject: 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 Reviewed-on: http://review.gluster.org/15187 Tested-by: Prasanna Kumar Kalever CentOS-regression: Gluster Build System Smoke: Gluster Build System NetBSD-regression: NetBSD Build System Reviewed-by: Atin Mukherjee Reviewed-by: Kotresh HR --- extras/stop-all-gluster-processes.sh | 4 ++-- 1 file 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}; } -- cgit