[
https://issues.apache.org/jira/browse/YARN-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966547#comment-15966547
]
Subru Krishnan commented on YARN-6234:
--------------------------------------
Thanks for your response [~botong]. Essentially there are 2 scenarios:
1. Second attempt on same node - In this case, UAMs on secondaries should not
fail. Instead they should simply re-register the _original_ attempt using the
{{AMRMToken}}. In essence, for UAMs, the process is similar to RM failover.
2. Second attempt on different node - YARN-6128 should address this use case.
> 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]
