[
https://issues.apache.org/jira/browse/MESOS-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139221#comment-16139221
]
Charles Allen commented on MESOS-7006:
--------------------------------------
So previously you could lie about cpus on a system via static allocation. Like
give {{*}} 8 CPUs but give {{cpu-hungry}} 8000 CPUs. This would cause things
launched against the {{*}} offers to have much lower CPU priority than things
against the {{cpu-hungry}} resources.
Like many things in mesos, what a "cpu" means (like what a "disk" means) has to
be pre-arranged between the administrators and the application owners to ensure
expectations are met.
Having "cpu" directly enforce CFS quotas will cause all these apps with "0.1
cpu" to suddenly behave VERY differently.
Am I understanding it correctly that this is the intended change in behavior?
> Launch docker containers with --cpus instead of cpu-shares
> ----------------------------------------------------------
>
> Key: MESOS-7006
> URL: https://issues.apache.org/jira/browse/MESOS-7006
> Project: Mesos
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Craig W
> Priority: Minor
> Fix For: 1.4.0
>
>
> docker 1.13 was recently released and it now has a new --cpus flag which
> allows a user to specify how many cpus a container should have. This is much
> simpler for users to reason about.
> mesos should switch to starting a container with --cpus instead of
> --cpu-shares, or at least make it configurable.
> https://blog.docker.com/2017/01/cpu-management-docker-1-13/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
