You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Xudong Ni (JIRA)" <ji...@apache.org> on 2018/05/04 15:03:00 UTC

[jira] [Assigned] (MESOS-8340) Add a no-enforce isolation option.

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

Xudong Ni reassigned MESOS-8340:
--------------------------------

    Assignee: Xudong Ni

> Add a no-enforce isolation option.
> ----------------------------------
>
>                 Key: MESOS-8340
>                 URL: https://issues.apache.org/jira/browse/MESOS-8340
>             Project: Mesos
>          Issue Type: Improvement
>          Components: containerization
>            Reporter: James Peach
>            Assignee: Xudong Ni
>            Priority: Major
>
> Some resource isolators ({{disk/du}}, {{disk/xfs}} and {{network/ports}}) have the ability to run in a no-enforce mode where they report resource usage but do not enforce the allocated resource limit. Rather than a separate flag for each possibility, we could add an agent flag named {{\-\-noenforce-isolation}} that causes the agent to log any limitation raised by the given list of isolators, but would not cause the container to be killed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)