---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71303/#review217370
---
Won't we need the allocated amount for each framework (leaf node)
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71303/#review217341
---
Bad review!
Reviews applied: [71303, 71301, 71269, 71258, 71257,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71303/#review217328
---
Bad review!
Reviews applied: [71303, 71301, 71269, 71258, 71257,
> On Aug. 19, 2019, 9:44 a.m., Benjamin Mahler wrote:
> > What's the thinking on taking the allocator's framework struct? Why not
> > just take the information we need so that we can keep the interface
> > self-contained?
One of the goals of this refactoring is to eliminate state duplication
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71303/#review217301
---
Bad review!
Reviews applied: [71303, 71301, 71269, 71258, 71257,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71303/#review217293
---
What's the thinking on taking the allocator's framework struct?
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71303/#review217263
---
Bad review!
Reviews applied: [71303, 71301, 71269, 71258, 71257,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71303/#review217256
---
Bad review!
Reviews applied: [71303, 71301, 71269, 71258, 71257,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71303/
---
Review request for mesos, Andrei Sekretenko and Benjamin Mahler.
Bugs:
