You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "SammiChen (JIRA)" <ji...@apache.org> on 2018/03/06 06:34:00 UTC
[jira] [Commented] (YARN-7652) Handle AM register requests
asynchronously in FederationInterceptor
[ https://issues.apache.org/jira/browse/YARN-7652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387355#comment-16387355 ]
SammiChen commented on YARN-7652:
---------------------------------
Hi [~botong], is it still on target for 2.9.1? If not, can we push it out from 2.9.1 to next release?
> Handle AM register requests asynchronously in FederationInterceptor
> -------------------------------------------------------------------
>
> Key: YARN-7652
> URL: https://issues.apache.org/jira/browse/YARN-7652
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: amrmproxy, federation
> Affects Versions: 2.9.0, 3.0.0
> Reporter: Subru Krishnan
> Assignee: Botong Huang
> Priority: Major
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org