[
https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subru Krishnan updated YARN-4888:
---------------------------------
Attachment: YARN-4888-WIP.patch
Thanks [~asuresh] for taking a look at the v0 patch and updating it to add a
{{SchedulerKey}} to define a composite key for scheduler requests. This makes
the patch bigger (:)) but is more cleaner as we can now address YARN-314.
Currently we have {{Priority}} and {{allocationRequestId}} (will default to _0_
for backward compatibility) as the composite keys. This changes also enables
future extensions for the {{SchedulerKey}}.
> Changes in RM AppSchedulingInfo for identifying resource-requests explicitly
> ----------------------------------------------------------------------------
>
> Key: YARN-4888
> URL: https://issues.apache.org/jira/browse/YARN-4888
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Subru Krishnan
> Assignee: Subru Krishnan
> Attachments: YARN-4888-WIP.patch, YARN-4888-v0.patch
>
>
> YARN-4879 puts forward the notion of identifying allocate requests
> explicitly. This JIRA is to track the changes in RM app scheduling data
> structures to accomplish it. Please refer to the design doc in the parent
> JIRA for details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
