[
https://issues.apache.org/jira/browse/MESOS-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582350#comment-14582350
]
Jie Yu commented on MESOS-2818:
-------------------------------
commit a97434bde5dd1722c0fe2985c370b67f3eb5b049
Author: Jie Yu <[email protected]>
Date: Wed Jun 10 11:17:53 2015 -0700
Added a SlaveTest to caputure the case when containerizer usage fails.
Review: https://reviews.apache.org/r/35305
commit b3a006ed5bb3ebd3841558cf0316f0cbac9dd18c
Author: Jie Yu <[email protected]>
Date: Tue Jun 9 12:49:51 2015 -0700
Added a slave integration test in MonitorTest.
Review: https://reviews.apache.org/r/35264
commit 8274c5e9ef46e297337999760e741d93710832f8
Author: Jie Yu <[email protected]>
Date: Tue Jun 9 11:51:22 2015 -0700
Refactored the ResourceMonitor to get statistics from the Slave.
Review: https://reviews.apache.org/r/35260
commit eaa992a47c485561d13116564f2ee6434de59164
Author: Jie Yu <[email protected]>
Date: Mon Jun 8 16:28:03 2015 -0700
Removed unused constaints from ResourceMonitor.
Review: https://reviews.apache.org/r/35259
> Pass 'allocated' resources for each executor to the resource estimator.
> -----------------------------------------------------------------------
>
> Key: MESOS-2818
> URL: https://issues.apache.org/jira/browse/MESOS-2818
> Project: Mesos
> Issue Type: Task
> Reporter: Jie Yu
> Assignee: Jie Yu
> Labels: twitter
>
> Resource estimator obviously need this information to calculate, say the
> usage slack. Now the question is how. There are two approaches:
> 1) Pass in the allocated resources for each executor through the
> 'oversubscribable()' interface.
> 2) Let containerizer return total resources allocated for each container when
> 'usages()' are invoked.
> I would suggest to take route (1) for several reasons:
> 1) Eventually, we'll need to pass in slave's total resources to the resource
> estimator (so that RE can calculate allocation slack). There is no way that
> we can get that from containerizer. The slave's total resources keep changing
> due to dynamic reservation. So we cannot pass in the slave total resources
> during initialization.
> 2) The current implementation of usages() might skip some containers if it
> fails to get statistics for that container (not an error). This will cause
> in-complete information to the RE.
> 3) We may want to calculate 'unallocated = total - allocated' so that we can
> send allocation slack as well. Getting 'total' and 'allocated' from two
> different components might result in inconsistent value. Remember that
> 'total' keeps changing due to dynamic reservation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
