[
https://issues.apache.org/jira/browse/MESOS-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Dukhovniy updated MESOS-7783:
--------------------------------
Attachment: GroupDeployIntegrationTest.log.zip
Here is a full log from our test suite. Every test suite starts it's own
marathon+master+agent+zk bundle and runs the individual tests sequentially.
There is a {{cleanUp}} after each test which removes all the apps ensuring a
clean plate for the next test.
The interesting part for you starts here:
{code:java}
consoleText211.txt:[39mDEBUG[0;39m[23:17:07
GroupDeployIntegrationTest-LocalMarathon-32799] [34mINFO [0;39m[23:17:07
GroupVersioningUtil$]
[/group-1/app-with-running-deployment-cannot-be-deleted-without-force]: new app
detected
...
{code}
> 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
> Priority: Critical
> 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)
