[
https://issues.apache.org/jira/browse/MESOS-9420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701351#comment-16701351
]
Joseph Wu commented on MESOS-9420:
----------------------------------
Perhaps you want to limit the number of +containers+ or executors, rather than
the number of tasks. Tasks in Mesos can appear in a variety of forms, like
processes, nested containers, or even threads. An executor is the closest
equivalent of a "pod" in Kubernetes.
A few possible questions:
1) Would you want the limit to apply equally to containers launched under the
Mesos vs Docker containerizers? i.e. a shared total, or an individual total?
2) What would you want to do if the agent ends up under-utilized after reaching
the max number of tasks/executors/pods? It is possible to launch a large
number of tiny executors.
3) How would you want to handle reserved resources (such as persistent volumes)
on nodes that have reached the maximum?
> Limit the number of tasks can be run on a host
> ----------------------------------------------
>
> Key: MESOS-9420
> URL: https://issues.apache.org/jira/browse/MESOS-9420
> Project: Mesos
> Issue Type: Improvement
> Components: agent
> Reporter: haoyuan ge
> Priority: Minor
>
> Operators may want to limit the number of tasks running on a single host.
> Like _kubelet --max-pods_ which can limit the total pods running on a host.
> Can we make mesos-agent limit the task number also?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
