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 "Bibin A Chundatt (JIRA)" <ji...@apache.org> on 2018/10/15 13:44:00 UTC
[jira] [Updated] (YARN-8481) AMRMProxyPolicies should accept
heartbeat response from new/unknown subclusters
[ https://issues.apache.org/jira/browse/YARN-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bibin A Chundatt updated YARN-8481:
-----------------------------------
Fix Version/s: 2.9.2
3.2.0
2.10.0
> AMRMProxyPolicies should accept heartbeat response from new/unknown subclusters
> -------------------------------------------------------------------------------
>
> Key: YARN-8481
> URL: https://issues.apache.org/jira/browse/YARN-8481
> Project: Hadoop YARN
> Issue Type: Bug
> Components: amrmproxy, federation
> Reporter: Botong Huang
> Assignee: Botong Huang
> Priority: Minor
> Fix For: 2.10.0, 3.2.0, 2.9.2
>
> Attachments: YARN-8481.v1.patch
>
>
> Currently BroadcastAMRMProxyPolicy assumes that we only span the application to the sub-clusters instructed by itself via _splitResourceRequests_. However, with AMRMProxy HA, second attempts of the application might come up with multiple sub-clusters initially without consulting the AMRMProxyPolicy at all. This leads to exceptions in _notifyOfResponse._ It should simply allow the new/unknown sub-cluster heartbeat responses.
--
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