[
https://issues.apache.org/jira/browse/YARN-7652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subru Krishnan updated YARN-7652:
---------------------------------
Description: We (cc [~goiri]/[~botong]) observed that the
{{FederationInterceptor}} in {{AMRMProxy}} (and consequently the AM) is blocked
if the _StateStore_ has outdated info about a _SubCluster_. This is because we
handle AM register requests synchronously. This jira proposes to move to async
similar to how we operate with allocate invocations. (was: We (cc
[~goiri]/[~botong]) observed that the {{FederationInterceptor}} in
{{AMRMProxy}} and consequently the application is blocked if the _StateStore_
has outdated info about a _SubCluster_. This is because we handle AM register
requests synchronously. This jira proposes to move to async similar to how we
operate with allocate invocations.)
> Handle AM register requests asynchronously in FederationInterceptor
> -------------------------------------------------------------------
>
> Key: YARN-7652
> URL: https://issues.apache.org/jira/browse/YARN-7652
> Project: Hadoop YARN
> Issue Type: Bug
> Components: amrmproxy, federation
> Affects Versions: 2.9.0, 3.0.0
> Reporter: Subru Krishnan
> Assignee: Botong Huang
>
> We (cc [~goiri]/[~botong]) observed that the {{FederationInterceptor}} in
> {{AMRMProxy}} (and consequently the AM) is blocked if the _StateStore_ has
> outdated info about a _SubCluster_. This is because we handle AM register
> requests synchronously. This jira proposes to move to async similar to how we
> operate with allocate invocations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
