This repository was archived by the owner on Aug 16, 2021. It is now read-only.
Cleanup spot requests with price-too-low status #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since
docker-machine rm --force ...
wasn't helpful for removing Spot Requests with "price-too-low" status, we need to use AWS CLI to do that.Additionally, in this PR
createDockerMachine
function doesn't use global vars anymoredestroyDockerMachine
function addedcleanup
function renamed tocleanupAndExit
and moved to the top to allow interruptions (Ctrl-C ) at early stagesHow to check
Run any experiment on r4.xlarge instance (usually their spot prices are increased, sign of high demand):
Something like that should appear after the 1st attempt to launch an instance:
-- and in web console the corresponding spot request should be in "cancelled" state.