[
https://issues.apache.org/jira/browse/YARN-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367838#comment-16367838
]
Botong Huang commented on YARN-7900:
------------------------------------
Hi [~asuresh], yes I understand. I don't think I am breaking this requirement
though. After the flattening, everything in {{List<SchedulingRequest>
schedulingRequests}} will still be put into the {{allocate}} call each time. I
did this change because it simplify the code a bit, and the code pattern
becomes more consistent with other channels, i.e. release, updates, blacklists.
Please let me know what you think.
> [AMRMProxy] AMRMClientRelayer for stateful FederationInterceptor
> ----------------------------------------------------------------
>
> Key: YARN-7900
> URL: https://issues.apache.org/jira/browse/YARN-7900
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Botong Huang
> Assignee: Botong Huang
> Priority: Major
> Attachments: YARN-7900.v1.patch, YARN-7900.v2.patch
>
>
> Inside stateful FederationInterceptor (YARN-7899), we need a component
> similar to AMRMClient that remembers all pending (outstands) requests we've
> sent to YarnRM, auto re-register and do full pending resend when YarnRM fails
> over and throws ApplicationMasterNotRegisteredException back. This JIRA adds
> this component as AMRMClientRelayer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
