mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Mahler (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MESOS-4547) Introduce TASK_KILLING state.
Date Tue, 23 Feb 2016 18:12:18 GMT

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

Benjamin Mahler edited comment on MESOS-4547 at 2/23/16 6:11 PM:
-----------------------------------------------------------------

{noformat}
commit 022be0a833dfb58de958a80eabc89fa9334782e0
Author: Abhishek Dasgupta <a10gupta@linux.vnet.ibm.com>
Date:   Sat Feb 20 12:56:24 2016 +0100

    Introduced a TASK_KILLING state.

    TASK_KILLING can be used to signify that the kill request has been
    received by the executor, but the task is not yet killed. This is
    similar to how TASK_STARTING indicates the launch request has been
    received by the executor, but the task is not yet launched.

    This new state will be guarded by a framework capability in order
    to ensure that we do not break older frameworks.

    Review: https://reviews.apache.org/r/43487/
{noformat}

{noformat}
commit cae9162a198a4a298fee920c57dbd128731529e2
Author: Abhishek Dasgupta <a10gupta@linux.vnet.ibm.com>
Date:   Sat Feb 20 13:09:16 2016 +0100

    Added a framework capability to guard TASK_KILLING.

    Frameworks must opt-in to receive TASK_KILLING. For now, it will be
    entirely the responsibility of the executor to check the capability
    before sending a TASK_KILLING update.

    Review: https://reviews.apache.org/r/43488/
{noformat}

{noformat}
commit a30233b994dd1a77eb8ef37525b5aa7b6ecdf3bd
Author: Abhishek Dasgupta <a10gupta@linux.vnet.ibm.com>
Date:   Sat Feb 20 14:25:15 2016 +0100

    Updated the command / docker executors to send TASK_KILLING.

    Review: https://reviews.apache.org/r/43489/
{noformat}

{noformat}
commit ee86b13633a9469629dbd79681d0776b6020f76a
Author: Benjamin Mahler <bmahler@apache.org>
Date:   Sat Feb 20 16:18:22 2016 +0100

    Added command executor tests for TASK_KILLING.
{noformat}

{noformat}
commit 978ccb5dd637f0e1577ecae1e21973f50429b04c
Author: Benjamin Mahler <bmahler@apache.org>
Date:   Sat Feb 20 17:28:58 2016 +0100

    Added docker executor tests for TASK_KILLING.
{noformat}

{noformat}
commit 1488f16d283f69b7dc96feaee91b04a09012ca4a
Author: Benjamin Mahler <bmahler@apache.org>
Date:   Sat Feb 20 17:35:30 2016 +0100

    Added TASK_KILLING to the API changes in the CHANGELOG.
{noformat}

{noformat}
commit 8b5137ddbb33417518dee32066c0fb552d05d046
Author: Benjamin Mahler <bmahler@apache.org>
Date:   Mon Feb 22 06:16:50 2016 +0100

    Updated the HA framework guide for TASK_KILLING.

    Review: https://reviews.apache.org/r/43821
{noformat}

{noformat}
commit b1092b005b03d231b18806679a8e1d58a09f3004
Author: Benjamin Mahler <bmahler@apache.org>
Date:   Mon Feb 22 10:03:30 2016 +0100

    Updated webui to reflect the new TASK_KILLING state.

    Review: https://reviews.apache.org/r/43888
{noformat}


was (Author: bmahler):
{noformat}
commit 022be0a833dfb58de958a80eabc89fa9334782e0
Author: Abhishek Dasgupta <a10gupta@linux.vnet.ibm.com>
Date:   Sat Feb 20 12:56:24 2016 +0100

    Introduced a TASK_KILLING state.

    TASK_KILLING can be used to signify that the kill request has been
    received by the executor, but the task is not yet killed. This is
    similar to how TASK_STARTING indicates the launch request has been
    received by the executor, but the task is not yet launched.

    This new state will be guarded by a framework capability in order
    to ensure that we do not break older frameworks.

    Review: https://reviews.apache.org/r/43487/
{noformat}

{noformat}
commit cae9162a198a4a298fee920c57dbd128731529e2
Author: Abhishek Dasgupta <a10gupta@linux.vnet.ibm.com>
Date:   Sat Feb 20 13:09:16 2016 +0100

    Added a framework capability to guard TASK_KILLING.

    Frameworks must opt-in to receive TASK_KILLING. For now, it will be
    entirely the responsibility of the executor to check the capability
    before sending a TASK_KILLING update.

    Review: https://reviews.apache.org/r/43488/
{noformat}

{noformat}
commit a30233b994dd1a77eb8ef37525b5aa7b6ecdf3bd
Author: Abhishek Dasgupta <a10gupta@linux.vnet.ibm.com>
Date:   Sat Feb 20 14:25:15 2016 +0100

    Updated the command / docker executors to send TASK_KILLING.

    Review: https://reviews.apache.org/r/43489/
{noformat}

{noformat}
commit ee86b13633a9469629dbd79681d0776b6020f76a
Author: Benjamin Mahler <bmahler@apache.org>
Date:   Sat Feb 20 16:18:22 2016 +0100

    Added command executor tests for TASK_KILLING.
{noformat}

{noformat}
commit 978ccb5dd637f0e1577ecae1e21973f50429b04c
Author: Benjamin Mahler <bmahler@apache.org>
Date:   Sat Feb 20 17:28:58 2016 +0100

    Added docker executor tests for TASK_KILLING.
{noformat}

{noformat}
commit 1488f16d283f69b7dc96feaee91b04a09012ca4a
Author: Benjamin Mahler <bmahler@apache.org>
Date:   Sat Feb 20 17:35:30 2016 +0100

    Added TASK_KILLING to the API changes in the CHANGELOG.
{noformat}

> Introduce TASK_KILLING state.
> -----------------------------
>
>                 Key: MESOS-4547
>                 URL: https://issues.apache.org/jira/browse/MESOS-4547
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Benjamin Mahler
>            Assignee: Abhishek Dasgupta
>              Labels: mesosphere
>             Fix For: 0.28.0
>
>
> Currently there is no state to express that a task is being killed, but is not yet killed
(see MESOS-4140). In a similar way to how we have TASK_STARTING to indicate the task is starting
but not yet running, a TASK_KILLING state would indicate the task is being killed but is not
yet killed.
> This would need to be guarded by a framework capability to protect old frameworks that
cannot understand the TASK_KILLING state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message