[
https://issues.apache.org/jira/browse/YARN-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397877#comment-15397877
]
Hudson commented on YARN-5440:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #10169 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10169/])
YARN-5440. Use AHSClient in YarnClient when TimelineServer is running.
(gtcarrera9: rev 26de4f0de789f58736d1dc383125cffb54debdd0)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/api/impl/YarnClientImpl.java
> Use AHSClient in YarnClient when TimelineServer is running
> ----------------------------------------------------------
>
> Key: YARN-5440
> URL: https://issues.apache.org/jira/browse/YARN-5440
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.9.0
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Fix For: 2.9.0, 3.0.0-alpha2
>
> Attachments: YARN-5440.1.patch
>
>
> In YarnClient, depends on whether we enable
> yarn.timeline-service.generic-application-history.enabled, the AHSClient will
> be used or not. But the AHSClientService is enabled by default when we start
> the TimelineServer which means we are able to get history information for
> applications/applicationAttempts/containers by using ahsClient when the
> TimelineServer is running. So, we do not have to rely on this deprecated
> configuration to get history information by using YarnClient.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
