Allow to start from the frostfs-adm prepared dump #42

New Issue

Open

opened 2023-08-02 12:20:14 +00:00 by fyrchik · 3 comments

fyrchik commented

2023-08-02 12:20:14 +00:00

Owner

frostfs-adm support morph init to the dump file. If I do multiple make down clean up during the development, I should have an option to not wait for >10 seconds just for frostfs-adm to deploy.

`frostfs-adm` support `morph init` to the dump file. If I do multiple `make down clean up` during the development, I should have an option to not wait for >10 seconds just for frostfs-adm to deploy.

fyrchik added the

discussion

good first issue

labels 2023-08-02 12:20:48 +00:00

alexvanin commented

2023-09-20 13:16:39 +00:00

Owner

As an alternative, frostfs-aio stores chain in the docker volume, so it is persistent between restarts and cleaned after make clean. Therefore first start takes >10 seconds, but then restarts are much faster. What do you think about it?

As an alternative, frostfs-aio stores chain in the docker volume, so it is persistent between restarts and cleaned after `make clean`. Therefore first start takes >10 seconds, but then restarts are much faster. What do you think about it?

fyrchik commented

2023-10-02 13:30:05 +00:00

Poster

Owner

It works, but I was thinking specifically about clean case, when I want to start with a fresh instance of node.

It works, but I was thinking specifically about `clean` case, when I want to start with a fresh instance of node.

alexvanin commented

2023-10-19 06:38:01 +00:00

Owner

Maybe some make dump and make restore commands can be useful. Default workflow isn't changed, but you can dump chain state at some point and then make down clean restore when you need to go back.

Maybe some `make dump` and `make restore` commands can be useful. Default workflow isn't changed, but you can dump chain state at some point and then `make down clean restore` when you need to go back.