forked from TrueCloudLab/frostfs-aio
[#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 <a.vanin@yadro.com>
This commit is contained in:
parent
0f46999aec
commit
ec15c7982d
1 changed files with 2 additions and 1 deletions
|
@ -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 &
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue