You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Charles Reiss (JIRA)" <ji...@apache.org> on 2011/06/07 07:05:58 UTC
[jira] [Created] (MESOS-18) LXC isolation module doesn't account
for queued task's resources usage
LXC isolation module doesn't account for queued task's resources usage
-----------------------------------------------------------------------
Key: MESOS-18
URL: https://issues.apache.org/jira/browse/MESOS-18
Project: Mesos
Issue Type: Bug
Components: isolation, slave
Environment: LXC isolation module; possibly other isolation modules.
Reporter: Charles Reiss
Priority: Minor
When sending queued tasks to a newly started executor, the slave calls resourcesChanged() in the isolation module before sending the queued tasks. LXC looks at counters that don't take the queued tasks usage into account when resizing the container for the new executor and is never triggered to reset the resource allocations again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MESOS-18) LXC isolation module doesn't account
for queued task's resources usage
Posted by "Charles Reiss (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Reiss resolved MESOS-18.
--------------------------------
Resolution: Duplicate
> LXC isolation module doesn't account for queued task's resources usage
> -----------------------------------------------------------------------
>
> Key: MESOS-18
> URL: https://issues.apache.org/jira/browse/MESOS-18
> Project: Mesos
> Issue Type: Bug
> Components: isolation, slave
> Environment: LXC isolation module; possibly other isolation modules.
> Reporter: Charles Reiss
> Priority: Minor
>
> When sending queued tasks to a newly started executor, the slave calls resourcesChanged() in the isolation module before sending the queued tasks. LXC looks at counters that don't take the queued tasks usage into account when resizing the container for the new executor and is never triggered to reset the resource allocations again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira