Thanks Benjamin, that's quite insightful and also a bummer. On Fri, Jan 29, 2016 at 11:50 AM Benjamin Mahler <[email protected]> wrote:
> Hey Charles, > > From this question it seems you're aware that the default allocator can be > swapped out for alternative implementations. However, the allocator module > interface is wide currently and so you'll be hard-pressed to find > implementations. (No refactoring took place during modularization). > Implementations will have had to keep up with a number of additional > responsibilities over time (generating inverse offers, handling quota, > etc). I'm thinking we'll need to figure out which pieces of functionality > *within* the allocator should be made modularizable when we do some of the > upcoming allocation work. For now, the expectation is that allocator module > implementations are non-trivial to maintain. > > Hope that helps! > > On Mon, Jan 25, 2016 at 3:18 PM, Charles Allen < > [email protected]> wrote: > >> Is there an allocator out there that will prioritize frameworks to favor >> the oldest first? >> >> I'm using spark in coarse mode, and I actually want the earliest >> registered course mode drivers to get as many resources as they want. >> > >
