mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qian Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-8713) Synchronize result of `wait` and `destroy` composing c'zer methods
Date Fri, 25 May 2018 01:34:00 GMT

    [ https://issues.apache.org/jira/browse/MESOS-8713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490098#comment-16490098
] 

Qian Zhang commented on MESOS-8713:
-----------------------------------

commit a4492f7767ef056bc4ea11f17d61521d547f38aa
Author: Andrei Budnik 
Date: Fri May 25 09:08:02 2018 +0800

Ensured that `wait()` and `destroy()` return the same result.
 
 We need to return the same `ContainerTermination` result for both
 `wait()` and `destroy()` for a terminated container. This patch
 ensures that for a terminated nested container `destroy()` returns
 the same result as for `wait()`.
 
 Review: https://reviews.apache.org/r/66670/

> Synchronize result of `wait` and `destroy` composing c'zer methods
> ------------------------------------------------------------------
>
>                 Key: MESOS-8713
>                 URL: https://issues.apache.org/jira/browse/MESOS-8713
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Andrei Budnik
>            Assignee: Andrei Budnik
>            Priority: Major
>             Fix For: 1.7.0
>
>
> Make sure both `wait` and `destroy` methods always return the same result.
> For example, if we call `destroy` forĀ a terminated nested container, then composing
c'zer returns `false`/`None`, while `wait` method calls `wait` for a parent container, which
might read a container termination status from the file. Probably, we need to implement a
test for this case, if it doesn't exist.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message