[
https://issues.apache.org/jira/browse/YARN-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966331#comment-15966331
]
Botong Huang commented on YARN-6234:
------------------------------------
Hi [~subru], today we don't support second attempt because the UAMs in the
secondary subclusters fail when the first attempt fails. When the UAM client
for the second attempt starts up, the application is already in failed state in
secondary subclusters.
What you suggested will work if the second attempt is in the same node as the
first attempt. However the problem still exists if the second attempt is
launched in a different node. I think we need to address this in UAM client in
Federation Interceptor.
> Support multiple attempts on the node when AMRMProxy is enabled
> ---------------------------------------------------------------
>
> Key: YARN-6234
> URL: https://issues.apache.org/jira/browse/YARN-6234
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: amrmproxy, federation, nodemanager
> Affects Versions: 2.8.0, 3.0.0-alpha1
> Reporter: Subru Krishnan
> Assignee: Giovanni Matteo Fumarola
> Attachments: YARN-6234-YARN-2915.v1.patch
>
>
> Currently {{AMRMProxy}} initializes an interceptor chain pipeline for every
> active AM in the node but it doesn't clean up & reinitialize correctly if
> there's a second attempt for any AM in the same node. This jira is to track
> the changes required to support multiple attempts on the node when AMRMProxy
> is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
