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

Stop or hibernate on-demand instances instead of terminating them. #348

Open
cristim opened this issue Jun 10, 2019 · 5 comments
Open

Stop or hibernate on-demand instances instead of terminating them. #348

cristim opened this issue Jun 10, 2019 · 5 comments

Comments

@cristim
Copy link
Member

cristim commented Jun 10, 2019

Github issue

Issue type

  • Feature Idea

Summary

Stop or hibernate each on-demand instance instead of terminating it, and then restart/resume it when a spot instance from the same AZ is being terminated.

This way we'll be able to quickly recover in case the spot instances inadvertently caused any sort of downtime, and also hopefully don't lose any capacity when the spot instances are being terminated.

@cristim
Copy link
Member Author

cristim commented Sep 18, 2019

We need to see how to do this in a way that doesn't cause us to leak these hibernated instances

@umitseremet
Copy link

During stopping the normal node after creating spot instead of him, which function is being applied? is that a graceful-shutdown or power-off effect?

@cristim
Copy link
Member Author

cristim commented Mar 9, 2020

@umitseremet currently we just use the usual API calls to detach and terminate instances in Autoscaling groups. This is a graceful termination much like when scaling in.

@umitseremet
Copy link

Thanks @cristim

@cristim
Copy link
Member Author

cristim commented Mar 10, 2020

@umitseremet no problem.

If you have further questions that are unrelated to any of the existing issues please raise them as new issues or just come and ask them on gitter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants