From ec15c7982ddb0fa028c066522a818f1036538481 Mon Sep 17 00:00:00 2001 From: Alex Vanin Date: Tue, 16 May 2023 16:56:07 +0300 Subject: [PATCH] [#3] Tick new epoch correctly during initialization During startup tick new epoch implicitly so the storage nodes are included in the network map. `tick.sh` script was removed. HEALTHY status of the storage node is not related to network map, so it is not necessary to tick epoch during health check. Signed-off-by: Alex Vanin --- bin/init-aio.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/bin/init-aio.sh b/bin/init-aio.sh index 1d76303..2572014 100755 --- a/bin/init-aio.sh +++ b/bin/init-aio.sh @@ -45,10 +45,11 @@ runServices() { while [[ -z "$(/usr/bin/frostfs-cli control healthcheck --endpoint localhost:16513 -c /config/cli-cfg-sn.yaml | grep 'Health status: READY')" ]]; do - ./bin/tick.sh sleep 5; done + /usr/bin/frostfs-adm morph force-new-epoch --config /config/frostfs-adm.yml || die "Failed to update epoch" + /usr/bin/frostfs-s3-gw --config /config/s3-gw-config.yaml & /usr/bin/frostfs-http-gw --config /config/http-gw-config.yaml & }