----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/42559/#review115541 -----------------------------------------------------------
Another problem is with Qos Controller, the slave may found that the resource estimator report 10 revocable cpus but the slave is using 20 revocable cpus, if the qos controller has logic of killing executors in such condition, then even if you offer the resources to those tasks, it will still be killed by qos controller. src/master/allocator/mesos/hierarchical.cpp (line 408) <https://reviews.apache.org/r/42559/#comment176520> When slave recover, the `revocable used` resources will also be reported back as `allocated`, this also cause some problem, as when `allocate()`, you are adding the resources which not coverted to `revocable`. - Guangya Liu On 一月 20, 2016, 5:01 p.m., Alexander Rukletsov wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/42559/ > ----------------------------------------------------------- > > (Updated 一月 20, 2016, 5:01 p.m.) > > > Review request for mesos, Bernd Mathiske, Joris Van Remoortere, Joseph Wu, > and Qian Zhang. > > > Bugs: MESOS-4441 > https://issues.apache.org/jira/browse/MESOS-4441 > > > Repository: mesos > > > Description > ------- > > See summary. > > > Diffs > ----- > > docs/quota.md 1a6d2f07fb74d168a7eb30764ab9ff80cea5e3b6 > src/master/allocator/mesos/hierarchical.cpp > e32ee4aa3ed9793bb5a99233e699e5cc2bdd796b > src/tests/hierarchical_allocator_tests.cpp > 953712149bd951789beb29c72779c4ac65aa48dc > > Diff: https://reviews.apache.org/r/42559/diff/ > > > Testing > ------- > > On Mac OS 10.10.4: > > `GTEST_FILTER="HierarchicalAllocatorTest.*" ./bin/mesos-tests.sh > --gtest_repeat=100 --gtest_break_on_failure --gtest_shuffle` > `make check` > > Updated `HierarchicalAllocatorTest.DRFWithQuota` succeeds with the change and > fails without. > > > Thanks, > > Alexander Rukletsov > >
