[
https://issues.apache.org/jira/browse/MESOS-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205795#comment-15205795
]
Jie Yu edited comment on MESOS-4827 at 3/22/16 4:53 AM:
--------------------------------------------------------
>From the log, it looks like files under /tmp/mesos/meta have been deleted by
>some entity (not Mesos itself). Are you on CentOS/RHEL? Can you double check
>your systemd-tmpfiles-clean.service see if it was cleaning files under /tmp?
Also, after you switch to use --work_dir=/var/lib/mesos, let us know if you
still have this problem.
was (Author: jieyu):
>From the log, it looks like files under /tmp/mesos/meta have been deleted by
>some entity (not Mesos itself). Are you on CentOS/RHEL? Can you double check
>your systemd-tmpfiles-clean.service see if it was cleaning files under /tmp?
> Destroy Docker container crashes Mesos slave
> --------------------------------------------
>
> Key: MESOS-4827
> URL: https://issues.apache.org/jira/browse/MESOS-4827
> Project: Mesos
> Issue Type: Bug
> Components: docker, framework, slave
> Affects Versions: 0.25.0, 0.26.0, 0.27.0, 0.28.0
> Reporter: Zhenzhong Shi
> Priority: Blocker
> Fix For: 0.29.0
>
>
> The details of this issue originally [posted on
> StackOverflow|http://stackoverflow.com/questions/35713985/destroy-docker-container-from-marathon-kills-mesos-slave].
>
> To be short, the problem is when we destroy/re-deploy a docker-containerized
> task, the mesos-slave got killed from time to time. It happened on our
> production environment and I cann't re-produce it.
> Please refer to the post on StackOverflow about the error message I got and
> details of environment info.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
