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 "Subru Krishnan (JIRA)" <ji...@apache.org> on 2018/07/09 18:57:00 UTC
[jira] [Commented] (YARN-8434) Nodemanager not registering to
active RM in federation
[ https://issues.apache.org/jira/browse/YARN-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537402#comment-16537402 ]
Subru Krishnan commented on YARN-8434:
--------------------------------------
Thanks [~bibinchundatt] for the patch. In our deployment, we have separate config (directories itself) for client and server as this allows us to not only control client behavior independent of server for scenarios exactly like this one but also is more secure as now all the server configs are being leaked/shared with clients. Will a similar approach work for you?
> Nodemanager not registering to active RM in federation
> ------------------------------------------------------
>
> Key: YARN-8434
> URL: https://issues.apache.org/jira/browse/YARN-8434
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bibin A Chundatt
> Assignee: Bibin A Chundatt
> Priority: Blocker
> Attachments: YARN-8434.001.patch, YARN-8434.002.patch
>
>
> FederationRMFailoverProxyProvider doesn't handle connecting to active RM.
--
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