Feature #15345
closed
[arvados-dispatch-cloud] kill container (management API)
Description
Described at Dispatching containers to cloud VMs:
POST /arvados/v1/dispatch/containers/kill?container_uuid=X terminates a container immediately.
- a single attempt is made to send SIGTERM to the container
- container state/priority fields are not affected
- assuming SIGTERM works, the container record will end up with state "Cancelled"
Currently (without this API) an admin can use the controller API to update the container's priority to 0, with similar results. This API is a bit more direct: it works even if the dispatcher isn't syncing with the controller properly/quickly, and it bypasses the TimeoutSignal config that rate-limits SIGTERM attempts per container.
Related issues
Updated by Tom Clegg over 5 years ago
- Blocks Idea #13908: [Epic] Replace SLURM for cloud job scheduling/dispatching added
Updated by Tom Morris over 5 years ago
- Target version changed from To Be Groomed to Arvados Future Sprints
- Story points set to 1.0
Updated by Tom Clegg over 5 years ago
- Status changed from New to In Progress
- Assigned To set to Tom Clegg
Updated by Tom Clegg over 5 years ago
15345-kill-container-api @ 49717fb59156c2b276ccc2fde0b9f2de71e812a6 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1326/
Updated by Tom Morris over 5 years ago
- Target version changed from Arvados Future Sprints to 2019-07-03 Sprint
Updated by Eric Biagiotti over 5 years ago
Tom Clegg wrote:
15345-kill-container-api @ 49717fb59156c2b276ccc2fde0b9f2de71e812a6 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1326/
This LGTM, if the tests are rerun and they pass. Thanks!
Updated by Tom Clegg over 5 years ago
15345-kill-container-api @ 49717fb59156c2b276ccc2fde0b9f2de71e812a6 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1338/
Updated by Tom Clegg over 5 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|1519b9e7e458a6fe286a214ee27ab07c3be6faf1.
Updated by