On 31 October 2013 17:01, Sandy Ryza <[email protected]> wrote:
> The ResourceRequest priority field is definitely used in the RM. In the > scheduler, requests within an application are keyed by it, and it's also > used for determining which resource request gets satisfied first within an > application. > > The reason we can't mix specific and non-specific requests is that the > scheduler stores a single ResourceRequest (with possible a large # > containers) per location per priority per app. > I see, it merges them. > > Check out AppSchedulingInfo.java for how this all works. > > The deeper issue is that the allocate protocol is fundamentally a little > lossy. It collapses requests into the data structures in > AppSchedulingInfo. Meaning there's no way to definitively tie a container > request to a container allocation. > > oh, I'm sure that the upper 24 bits of the priority field can do it at the expense of memory somewhere in the RM. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
