[
https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985900#comment-13985900
]
Vinod Kumar Vavilapalli commented on YARN-1963:
-----------------------------------------------
[~sunilg], thanks for taking this up. This is a really useful feature!
Before we jump into patches, we should consider writing up a small design doc
that describes the requirements and the mechanism of implementation - not
necessarily class-level design. There are few things to consider on the top of
my head:
- Values of priorities - static values like you described before or few known
priorities backed by integers leaving gaps for more powerful interaction with
priorities
- ACLs on priorities - If we don't have some such mechanism, users will all be
incentivized to submit apps all with the highest priority.
- The classic priority inversion problem: MAPREDUCE-314
I am sure there are more things to consider once we start thinking through
this. I can help write this down, let me know what you think.
> Support priorities across applications within the same queue
> -------------------------------------------------------------
>
> Key: YARN-1963
> URL: https://issues.apache.org/jira/browse/YARN-1963
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: api, resourcemanager
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
>
> It will be very useful to support priorities among applications within the
> same queue, particularly in production scenarios. It allows for finer-grained
> controls without having to force admins to create a multitude of queues, plus
> allows existing applications to continue using existing queues which are
> usually part of institutional memory.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
