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

[EC2 Specific] Need automated worker monitoring/restart #4

Open
ChristopherWilks opened this issue Mar 24, 2020 · 0 comments
Open

[EC2 Specific] Need automated worker monitoring/restart #4

ChristopherWilks opened this issue Mar 24, 2020 · 0 comments

Comments

@ChristopherWilks
Copy link
Collaborator

We currently use Vagrant to manage VMs in EC2 for recount-pump runs.

However, node management is ad hoc---each node has its own Vagrant process and subdirectory.

Node failures, either due to workflow specific problems (e.g. running out of disk space) or because nodes were pre-empted (spot market) need to be manually detected currently.

For a few tranches this is fine, for longer term runs, we may want to either try to use existing orchestration tools or roll our own to support the mix of inside/outside container code we're using.

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