[
https://issues.apache.org/jira/browse/MESOS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153964#comment-13153964
]
[email protected] commented on MESOS-56:
----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2669/
-----------------------------------------------------------
(Updated 2011-11-21 03:23:26.723463)
Review request for mesos.
Summary
-------
This calls Executor::addTask to accumulate the usage of queued tasks before
calling resourcesChanged() to ensure the executor has enough resources to run
those queued tasks.
This addresses bug MESOS-56.
https://issues.apache.org/jira/browse/MESOS-56
Diffs (updated)
-----
src/slave/slave.cpp de5716c
src/tests/master_tests.cpp 2438114
src/tests/utils.hpp 02772f7
Diff: https://reviews.apache.org/r/2669/diff
Testing
-------
Modification to MasterTest included.
Thanks,
Charles
> Resources of tasks queued during executor launch not always accounted for
> -------------------------------------------------------------------------
>
> Key: MESOS-56
> URL: https://issues.apache.org/jira/browse/MESOS-56
> Project: Mesos
> Issue Type: Bug
> Components: isolation, slave
> Reporter: Charles Reiss
> Assignee: Charles Reiss
>
> When initially launching an executor, the slave queues the tasks sent to the
> executor until the executor registers itself with the slave. When this
> happens, the slave calls resourcesChanged() on the isolation module, but
> before it adds the usage of the queued tasks.
--
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
