[
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-v2.patch
Clean patch with new tests for checking allocation request ids for both
{{Capacity/FairScheduler}} post rebase with YARN-5392.
The patch is complete and covers e2e scenarios except for:
1. Having multiple node/rack local requests for same *Priority* by using
different *AllocationRequestIds*. This is essentially the remaining work for
YARN-314.
2. Recreating *AllocationRequestId* for recovered *Containers* if RM fails
over. This might cause an issue only if RM fails over before notifying the AM
about newly allocated container(s). I have created YARN-5447 to track this.
> 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-4888-v2.patch, YARN-4888.001.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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
