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.

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

Start all required services via init-sequence #31

Open
alex-kononovich opened this issue Aug 21, 2018 · 0 comments
Open

Start all required services via init-sequence #31

alex-kononovich opened this issue Aug 21, 2018 · 0 comments

Comments

@alex-kononovich
Copy link
Member

Currently we have to launch state-service, front-service and init-service manually via websocket, because init-service cannot be started before previous two are launched and successfully checked in.

The way init-sequence currently works does not allow to simply list services in init sequence, because while it does launch containers in sequence, but it doesn't wait for checkin message from them, so it's quite possible that required containers won't start in time for init-service to launch.

Possible fix for that could be to extend Hexfile syntax in a way that it's possible to declare a dependency of one service on another (or rather list of dependencies), and wait for dependencies to send their checkin messages before starting dependent container.

@alex-kononovich alex-kononovich changed the title Start all required services through init-sequence Start all required services via init-sequence Aug 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant