[
https://issues.apache.org/jira/browse/MESOS-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316519#comment-16316519
]
Benno Evers commented on MESOS-8359:
------------------------------------
>From what I gather, the following conditions need to be met to reproduce:
- The other tasks on the slave need to be health-checked by a `COMMAND`-type
health check
- Docker executor must be used for all launched tasks
I'm also wondering which command was actually used for the command health
check, and if the executor and/or master logs at the time the bug is observed
show anything interesting?
Finally, since I'm not very experienced with Marathon, can you give some more
details on what exactly it means to "create a marathon application from your
image"?
> Health checks are flapping for all tasks on the slave if one task has no
> enough resources to run
> ------------------------------------------------------------------------------------------------
>
> Key: MESOS-8359
> URL: https://issues.apache.org/jira/browse/MESOS-8359
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.3.2
> Reporter: Viacheslav Valyavskiy
> Attachments: logs2
>
>
> I have attached some logs from the affected
> slave(newappmv_qagame_testapp.green_csahttp - name of the 'bad' application)
> Steps to reproduce:
> 1. Run multiple tasks on the slave
> 2. Create marathon application from our image ( docker pull
> vvalyavskiy/csa-http ) and set memory limit to 16MB for it.
> 3. Wait some time and then observe flapping of all tasks on the slave where
> our task is started
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
