[
https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491959#comment-14491959
]
Craig Welch commented on YARN-3318:
-----------------------------------
added comments to compoundcomparator, re-introduced getId (in lieu of getName),
switched to ResourceUsage - to avoid unnecessary dependency on [YARN-3361]
SchedularApplicationAttempt manages pending in a way it won't have to long
term, this doesn't effect the api and allows these to be committed in any
order. Sticking with "Scheduling" instead of "Cached" as suggested earlier by
[~vinodkv] to keep it's purpose clear (Cached is too general) and because it
can't be used as a generalized "cache" of the values, the lifecycle is tied to
use by OrderingPolicies.
> Create Initial OrderingPolicy Framework and FifoOrderingPolicy
> --------------------------------------------------------------
>
> Key: YARN-3318
> URL: https://issues.apache.org/jira/browse/YARN-3318
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: scheduler
> Reporter: Craig Welch
> Assignee: Craig Welch
> Attachments: YARN-3318.13.patch, YARN-3318.14.patch,
> YARN-3318.17.patch, YARN-3318.34.patch, YARN-3318.35.patch,
> YARN-3318.36.patch, YARN-3318.39.patch, YARN-3318.45.patch,
> YARN-3318.47.patch, YARN-3318.48.patch, YARN-3318.52.patch,
> YARN-3318.53.patch, YARN-3318.56.patch
>
>
> Create the initial framework required for using OrderingPolicies and an
> initial FifoOrderingPolicy
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
