[jira] [Updated] (MESOS-7801) Retry logic for unsuccessful `docker rm` during agent recovery

2017-08-03 Thread Anand Mazumdar (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anand Mazumdar updated MESOS-7801:
--
Fix Version/s: (was: 1.4.0)

> Retry logic for unsuccessful `docker rm` during agent recovery
> --
>
> Key: MESOS-7801
> URL: https://issues.apache.org/jira/browse/MESOS-7801
> Project: Mesos
>  Issue Type: Improvement
>  Components: docker
>Reporter: Chun-Hung Hsiao
>Assignee: Chun-Hung Hsiao
>
> In MESOS- we skip the failure when `docker rm` fails due to mount leakage 
> during agent recovery. In order not to leave residual docker containers in 
> the docker daemon, we could do a best-effort `docker rm` retry with an 
> exponential backoff since we cannot control when the leakage would be 
> terminated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (MESOS-7801) Retry logic for unsuccessful `docker rm` during agent recovery

2017-08-03 Thread Adam B (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-7801:
--
Sprint: Mesosphere Sprint 59  (was: Mesosphere Sprint 59, Mesosphere Sprint 
60)

> Retry logic for unsuccessful `docker rm` during agent recovery
> --
>
> Key: MESOS-7801
> URL: https://issues.apache.org/jira/browse/MESOS-7801
> Project: Mesos
>  Issue Type: Improvement
>  Components: docker
>Reporter: Chun-Hung Hsiao
>Assignee: Chun-Hung Hsiao
> Fix For: 1.4.0
>
>
> In MESOS- we skip the failure when `docker rm` fails due to mount leakage 
> during agent recovery. In order not to leave residual docker containers in 
> the docker daemon, we could do a best-effort `docker rm` retry with an 
> exponential backoff since we cannot control when the leakage would be 
> terminated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (MESOS-7801) Retry logic for unsuccessful `docker rm` during agent recovery

2017-07-21 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-7801:
--
Sprint: Mesosphere Sprint 59, Mesosphere Sprint 60  (was: Mesosphere Sprint 
59)

> Retry logic for unsuccessful `docker rm` during agent recovery
> --
>
> Key: MESOS-7801
> URL: https://issues.apache.org/jira/browse/MESOS-7801
> Project: Mesos
>  Issue Type: Improvement
>  Components: docker
>Reporter: Chun-Hung Hsiao
>Assignee: Chun-Hung Hsiao
> Fix For: 1.4.0
>
>
> In MESOS- we skip the failure when `docker rm` fails due to mount leakage 
> during agent recovery. In order not to leave residual docker containers in 
> the docker daemon, we could do a best-effort `docker rm` retry with an 
> exponential backoff since we cannot control when the leakage would be 
> terminated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)