From f72331f4acbdf2794f6373f552da9e5355fef6e2 Mon Sep 17 00:00:00 2001 From: Prasanna Kumar Kalever Date: Fri, 16 Sep 2016 12:55:37 +0530 Subject: [PATCH 38/86] 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 Backport of: > 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 Change-Id: I2d2176f2bf5014f3afd622194a8b2d60c86926af BUG: 1294754 Signed-off-by: Prasanna Kumar Kalever Reviewed-on: https://code.engineering.redhat.com/gerrit/84767 Reviewed-by: Atin Mukherjee --- extras/stop-all-gluster-processes.sh | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/extras/stop-all-gluster-processes.sh b/extras/stop-all-gluster-processes.sh index f11c634..69fd601 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}; } -- 1.7.1