[
https://issues.apache.org/jira/browse/YARN-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883906#comment-13883906
]
Hudson commented on YARN-1642:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5052 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5052/])
YARN-1642. RMDTRenewer#getRMClient should use ClientRMProxy (kasha) (kasha:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1561990)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/security/client/RMDelegationTokenIdentifier.java
> RMDTRenewer#getRMClient should use ClientRMProxy
> ------------------------------------------------
>
> Key: YARN-1642
> URL: https://issues.apache.org/jira/browse/YARN-1642
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.4.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Priority: Blocker
> Fix For: 2.3.0
>
> Attachments: yarn-1642-1.patch
>
>
> RMDTRenewer#getRMClient gets a proxy to the RM in the conf directly instead
> of going through ClientRMProxy.
> {code}
> final YarnRPC rpc = YarnRPC.create(conf);
> return
> (ApplicationClientProtocol)rpc.getProxy(ApplicationClientProtocol.class,
> addr, conf);
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
