From a462e1f3146ad1c0e1099bbc4d0f5269a1c02545 Mon Sep 17 00:00:00 2001 From: Mohammed Rafi KC Date: Fri, 3 Jul 2015 15:27:15 +0530 Subject: tiering/glusterd: start tier daemon during volume start Tier daemon should always run with tier volume. If volume is stopped and started again, we manually need to start the tier-daemon, instead this patch will automatically trigger tier process along with volume start. A snapshot restored volume will not have node_state_info, so we need to create and store it dynamically Change-Id: I659387c914bec7a1b6929ee5cb61f7b406402075 BUG: 1238593 Signed-off-by: Mohammed Rafi KC Signed-off-by: Dan Lambright Reviewed-on: http://review.gluster.org/11525 Tested-by: NetBSD Build System Tested-by: Gluster Build System Reviewed-by: Krishnan Parthasarathi --- tests/basic/tier/tier.t | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'tests/basic') diff --git a/tests/basic/tier/tier.t b/tests/basic/tier/tier.t index 337f7d7f3e7..e8f17f32473 100755 --- a/tests/basic/tier/tier.t +++ b/tests/basic/tier/tier.t @@ -137,6 +137,11 @@ TEST ! $CLI volume set $V0 cluster.tier-demote-frequency 4 TEST ! $CLI volume detach-tier $V0 commit force TEST $CLI volume attach-tier $V0 replica 2 $H0:$B0/${V0}$CACHE_BRICK_FIRST $H0:$B0/${V0}$CACHE_BRICK_LAST + +# stop the volume and restart it. The rebalance daemon should restart. +TEST $CLI volume stop $V0 +TEST $CLI volume start $V0 + sleep_first_cycle $CLI volume rebalance $V0 tier status -- cgit