[
https://issues.apache.org/jira/browse/MESOS-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
niuminguo updated MESOS-7906:
-----------------------------
Description:
I found mesos send the wrong docker container data in statusUpdate when task
health check is set.
I have one app with two tasks: task1 and task2, set healthy check for each
task. when task become running(health is false), i got the
container data from status update event and which is correct. when health is
true, i received status update event again and found the container data is
wrong: `task1` has the container data which is belong to `task2`.
was:
I found mesos send the wrong docker container data in statusUpdate when task
health check is set.
I have one app with two tasks: task1 and task2, set healthy check for each
task. when task become running(health is false), i got the
container data from status update event and which is correct. when health is
true, i received status update event again and found the container data is
wrong: task1 has the container data which is belong to task2.
> mesos send the wrong container data while health check is set
> -------------------------------------------------------------
>
> Key: MESOS-7906
> URL: https://issues.apache.org/jira/browse/MESOS-7906
> Project: Mesos
> Issue Type: Bug
> Components: executor
> Affects Versions: 1.3.0
> Reporter: niuminguo
> Labels: health-check
>
> I found mesos send the wrong docker container data in statusUpdate when task
> health check is set.
> I have one app with two tasks: task1 and task2, set healthy check for each
> task. when task become running(health is false), i got the
> container data from status update event and which is correct. when health is
> true, i received status update event again and found the container data is
> wrong: `task1` has the container data which is belong to `task2`.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
