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] [Updated] (MESOS-7783) Framework might not receive status update when a just launched task is killed immediately
Date Wed, 16 Aug 2017 19:05:00 GMT

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

Benjamin Mahler updated MESOS-7783:
-----------------------------------
    Target Version/s: 1.1.3, 1.2.3, 1.3.2, 1.4.0  (was: 1.2.3, 1.3.2, 1.4.0)

> Framework might not receive status update when a just launched task is killed immediately
> -----------------------------------------------------------------------------------------
>
>                 Key: MESOS-7783
>                 URL: https://issues.apache.org/jira/browse/MESOS-7783
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.2.0
>            Reporter: Benjamin Bannier
>            Assignee: Benjamin Mahler
>            Priority: Blocker
>              Labels: reliability
>         Attachments: GroupDeployIntegrationTest.log.zip, logs
>
>
> Our Marathon team are seeing issues in their integration test suite when Marathon gets
stuck in an infinite loop trying to kill a just launched task. In their test a task launched
which is immediately followed by killing the task -- the framework does e.g., not wait for
any task status update.
> In this case the launch and kill messages arrive at the agent in the correct order, but
both the launch and kill paths in the agent do not reach the point where a status update is
sent to the framework. Since the framework has seen no status update on the task it re-triggers
a kill, causing an infinite loop.



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

Mime
View raw message