Priorities are within you application. You always get P0 containers before you get P1 containers and so on....
Arun On Sep 22, 2011, at 2:23 PM, Chris Riccomini wrote: > Hey Arun, > > I think I see. Basically, 2646's patch is using the priority number as an ID > for a container (or group of containers) within an AllocateRequest. > > So, in my scenario, I could set ResourceRequest 1 to priority 1, and > ResourceRequest 2 to priority 2, and (with this patch) get the priority back > out on the other end. Is this correct? > > Are priorities cross-application, or just for containers within the > application? > > Cheers, > Chris > > On 9/22/11 2:13 PM, "Arun C Murthy" <a...@hortonworks.com> wrote: > >> Also, for now you can assume it's the highest outstanding priority or wait >> for >> MR-2646. >> >> On Sep 22, 2011, at 1:44 PM, Chris Riccomini wrote: >> >>> Hey Guys, >>> >>> I’m sure there’s a way to do this, but I’m missing it. >>> >>> If I have an AllocateRequest with multiple ResourceRequests in it (say 2), >>> and I get two containers back, how do I map which container was sent back >>> for >>> which ResourceRequest? >>> >>> Thanks! >>> Chris >> >
