You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Tomasz Janiszewski (JIRA)" <ji...@apache.org> on 2017/05/06 10:08:04 UTC

[jira] [Commented] (MESOS-7006) Launch docker containers with --cpus instead of cpu-shares

    [ https://issues.apache.org/jira/browse/MESOS-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999370#comment-15999370 ] 

Tomasz Janiszewski commented on MESOS-7006:
-------------------------------------------

I discarded patch https://reviews.apache.org/r/56193/ after introducing docker run options class there is no need to use cpus and add additional logic to achieve same result as we have with current implementation.

> 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
>            Assignee: Tomasz Janiszewski
>            Priority: Minor
>
> 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.3.15#6346)