[
https://issues.apache.org/jira/browse/YARN-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849816#comment-13849816
]
Karthik Kambatla commented on YARN-1028:
----------------------------------------
For the log message in YarnClientImpl, it is hard to fetch the RM
InetSocketAddress we are connecting to. In the HA case,
ConfiguredRMFailoverProxyProvider takes care of connecting to the correct RM
and failing over, transparent to the client. If we want the client to know this
information, we need to bubble this information up. Even then, the only way to
know is on connection to the RM. For this, may be it is better for submit
application to return the RM address we submitted to. This seems like an
overkill for something as trivial as a Log. I think it should be sufficient to
show a list of the RM addresses. No?
As Vinod suggested, I can get rid of the rmAddress field altogether and show
the list of RMs.
> Add FailoverProxyProvider like capability to RMProxy
> ----------------------------------------------------
>
> Key: YARN-1028
> URL: https://issues.apache.org/jira/browse/YARN-1028
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Karthik Kambatla
> Attachments: yarn-1028-1.patch, yarn-1028-2.patch, yarn-1028-3.patch,
> yarn-1028-4.patch, yarn-1028-5.patch, yarn-1028-6.patch, yarn-1028-7.patch,
> yarn-1028-8.patch, yarn-1028-9.patch, yarn-1028-draft-cumulative.patch
>
>
> RMProxy layer currently abstracts RM discovery and implements it by looking
> up service information from configuration. Motivated by HDFS and using
> existing classes from Common, we can add failover proxy providers that may
> provide RM discovery in extensible ways.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
