[
https://issues.apache.org/jira/browse/MESOS-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949063#comment-13949063
]
Chengwei Yang commented on MESOS-1100:
--------------------------------------
The file src/slave/cgroups_isolator.cpp was deleted in below commit.
commit f90fe7641ea8f7066a6a1171a24ddaa8dc30e789
Author: Ian Downes <[email protected]>
Date: Tue Feb 11 16:24:59 2014 -0800
Containerizer (part 1)
The proposed Containerizer interface is to replace the existing
Isolator.
One ContainerizerProcess has been written:
MesosContainerizerProcess - implements containerizeration internally
using a Launcher and one or more Isolators (following review)
The intent is to also support a generic ExternalContainerizerProcess
that can delegate containerizeration by making external calls. Other
Containerizers could interface with specific external containerization
techniques such as Docker or LXC.
Review: https://reviews.apache.org/r/16147
So I think this is not an issue any more.
> Drop "OOM notifier is triggered" log message
> --------------------------------------------
>
> Key: MESOS-1100
> URL: https://issues.apache.org/jira/browse/MESOS-1100
> Project: Mesos
> Issue Type: Bug
> Components: slave
> Reporter: Suman Karumuri
> Priority: Minor
> Labels: newbie
> Fix For: 0.19.0
>
>
> Currently, a slave prints a message similar to the one below during a cgroup
> cleanup even when no OOM was thrown. The confusing message should be removed.
> I0314 18:13:38.940258 49459 cgroups_isolator.cpp:1192] OOM notifier is
> triggered for executor
> thermos-1394230111935-timelineservice-prod-fanoutservice-activity-prod-71-5c22aef6-4415-40a1-bada-1f3b443fd16e
> of framework 201104070004-0000002563-0000 with uuid
> de0da555-aa91-4df4-8f08-9fd441646200
--
This message was sent by Atlassian JIRA
(v6.2#6252)
