[
https://issues.apache.org/jira/browse/MESOS-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902258#comment-14902258
]
Chengwei Yang commented on MESOS-3488:
--------------------------------------
Hi [[email protected]], we use mesos in product environment, the next version
we'll upgrade to is 0.23, but have to first move mesos 0.21 to centos7.
BTW, I think I found a hint, /sys/fs/cgroup/memory ctime changed after
mesos-slave running for a while, I think this is the root cause, I'll see why
/sys/fs/cgroup/memory changed, maybe remounted and why.
> /sys/fs/cgroup/memory/mesos missing after running a while
> ---------------------------------------------------------
>
> Key: MESOS-3488
> URL: https://issues.apache.org/jira/browse/MESOS-3488
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.21.0
> Environment: mesos 0.21.0 on CentOS 7.1
> Reporter: Chengwei Yang
>
> I setup mesos 0.21.0 on CentOS 7.1 with mesos-0.21.0 rpm downloaded from
> mesosphere.
> at first, it works fine, jobs are finished correctly, however, after running
> a while, all task goes to LOST.
> And there is nothing in **sandbox** and I see below from mesos-slave.ERROR
> ```
> E0922 14:02:31.329264 8336 slave.cpp:2787] Container
> '865c9a1c-3abe-4263-921e-8d0be2f0a56d' for executor
> '21bf1400-6456-45e5-8f28-fe5ade7e7bfd' of framework
> '20150401-105258-3755085578-5050-14676-0000' failed to start: Failed to
> prepare isolator: Failed to create directory
> '/sys/fs/cgroup/memory/mesos/865c9a1c-3abe-4263-921e-8d0be2f0a56d': No such
> file or directory
> ```
> And I checked that /sys/fs/cgroup/cpu/mesos does exist while
> /sys/fs/cgroup/memory/mesos is missing.
> Since at first mesos works fine (and I checked source code, that if it create
> /sys/fs/cgroup/memory/mesos failed at mesos-slave startup, it will log that
> error), so I'm curious when/which removed /sys/fs/cgroup/memory/mesos.
> Has anyone saw this issue before?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
