Skip to content
This repository has been archived by the owner on Jul 16, 2020. It is now read-only.

Handle corrupt instances #4

Open
markdryan opened this issue Apr 7, 2016 · 0 comments
Open

Handle corrupt instances #4

markdryan opened this issue Apr 7, 2016 · 0 comments

Comments

@markdryan
Copy link
Contributor

We need some sort of strategy for handling corrupt instances. For example, launcher might detect on start up that the state it maintains about an instance has become corrupted, or the docker container associated by with that instance has been deleted.

Currently, if launcher cannot retrieve an instance state it simply ignores it. This means that it is not reported to the upper layers, and so cannot be deleted, and is essentially leaked on the compute node.

Special handling is also required for instances associated with docker containers that get deleted by some out of bound mechanism, i.e., by someone logging into the compute node and doing

sudo docker rm -f

@markdryan markdryan self-assigned this Apr 7, 2016
@markdryan markdryan added the P2 label Jun 6, 2016
@sameo sameo added P3 and removed P2 labels Jun 9, 2016
kaccardi referenced this issue in kaccardi/ciao Aug 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants