Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change the order of shutdown for down command #701

Open
ghost opened this issue Aug 31, 2020 · 0 comments
Open

Change the order of shutdown for down command #701

ghost opened this issue Aug 31, 2020 · 0 comments
Assignees
@reliveyy
Labels
enhancement New feature or request P3 low priority

Comments

@ghost
Copy link

ghost commented Aug 31, 2020 •
edited by kilrau
Loading

Current implementation:

mainnet > down
Stopping bitcoind...
Stopping litecoind...
Stopping geth...
Stopping lndbtc...
Stopping lndltc...
Stopping connext...
Stopping boltz...
Stopping xud...
Removing bitcoind...
Removing litecoind...
Removing geth...
Removing lndbtc...
Removing lndltc...
Removing connext...
Removing boltz...
Removing xud...
Removing network mainnet_default

Desired order of container shutdown is Layer3 -> Layer2 -> Layer1:

--- Layer 3
Stopping boltz...
Stopping xud...
--- Layer 2
Stopping lndbtc...
Stopping lndltc...
Stopping connext...
--- Layer 1
Stopping bitcoind...
Stopping litecoind...
Stopping geth...

Bonus points: we could also attempt to stop same layer clients in parallel to speed it up.
@kilrau kilrau added the P3 low priority label Aug 31, 2020
@kilrau kilrau added the enhancement New feature or request label Aug 31, 2020
@kilrau kilrau mentioned this issue Oct 21, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@reliveyy reliveyy

Labels
enhancement New feature or request P3 low priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@reliveyy @kilrau