You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2016/07/22 23:13:20 UTC

[jira] [Updated] (MESOS-5885) max_executors_per_agent does not take effect on mesos docker executor

     [ https://issues.apache.org/jira/browse/MESOS-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jie Yu updated MESOS-5885:
--------------------------
    Labels: mesosphere  (was: )

> max_executors_per_agent does not take effect on mesos docker executor
> ---------------------------------------------------------------------
>
>                 Key: MESOS-5885
>                 URL: https://issues.apache.org/jira/browse/MESOS-5885
>             Project: Mesos
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.27.3, 0.28.2, 1.0.0
>         Environment: centos 7.2
>            Reporter: Qi Feng
>              Labels: mesosphere
>
> I build mesos-1.0.0-rc2 with network isolator in centos 7.2. And try to set max_executors_per_agent=10 to test if docker task would be limited in 10 on every mesos agent. In fact, my case is launching 40 tasks (0.1core 0.1M mem each) on three different agent machine, and both agent launched more than 10 tasks.
> I found mesos master hold executor data in a haspmap, and the key is ExecutorID.
> https://github.com/apache/mesos/blob/1.0.x/src/master/master.hpp#L306
> https://github.com/apache/mesos/blob/1.0.x/src/master/master.cpp#L5747
> Then I get state.json from mesos master to looking for any executor information. Then I found executer_id is empty string in taskInfo json. Is there any relation between the empty executor id and max_executors_per_agent issue?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)