You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Hindman (JIRA)" <ji...@apache.org> on 2013/03/03 22:57:12 UTC
[jira] [Commented] (MESOS-372) cgroups fail if executor-id contains
slashes
[ https://issues.apache.org/jira/browse/MESOS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591879#comment-13591879 ]
Benjamin Hindman commented on MESOS-372:
----------------------------------------
This is yet another example of where doing LOG(FATAL) is unfortunate. This killed the slave but could have just killed the executor/task.
> cgroups fail if executor-id contains slashes
> --------------------------------------------
>
> Key: MESOS-372
> URL: https://issues.apache.org/jira/browse/MESOS-372
> Project: Mesos
> Issue Type: Bug
> Environment: ubuntu 12.04
> Reporter: Florian Leibert (flo)
>
> Output:
> I0303 21:45:01.130616 32584 paths.hpp:234] Created executor directory '/tmp/mesos/slaves/201302210202-
> 1899048714-5050-24408-251/frameworks/chronos/executors//srv/mesos/utils/async-executor.arx/runs/c193bb95-f0aa-4ddd-bfe1-79bffb90dc15'
> I0303 21:45:01.132333 32587 cgroups_isolation_module.cpp:436] Launching /srv/mesos/utils/async-executor.arx (/srv/mesos/utils/async-executor.arx) in /tmp/mesos/slaves/201302210202-1899048714-5050-24408-251/frameworks/chronos/executors//srv/mesos/utils/async-executor.arx/runs/c193bb95-f0aa-4ddd-bfe1-79bffb90dc15 with resources for framework chronos in cgroup mesos/framework_chronos_executor_/srv/mesos/utils/async-executor.arx_tag_35cc03da-eb2f-4aca-9b63-527f0f185e18
> F0303 21:45:01.142719 32587 cgroups_isolation_module.cpp:480] Failed to create cgroup for executor /srv/mesos/utils/async-executor.arx of framework chronos: Failed to create directory at /cgroup/mesos/framework_chronos_executor_/srv/mesos/utils/async-executor.arx_tag_35cc03da-eb2f-4aca-9b63-527f0f185e18: No such file or directory
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira