[
https://issues.apache.org/jira/browse/YARN-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396656#comment-15396656
]
Xuan Gong commented on YARN-5440:
---------------------------------
Thanks for the review. [~gtCarrera9]
Created https://issues.apache.org/jira/browse/YARN-5442 to track the testcase
failures.
bq. if the user turn off timeline service but enable AHS in the config.
So, the configuration:
yarn.timeline-service.generic-application-history.enabled is deprecated
configuration which means we could remove this configuration without any impact
(If i understand the deprecate correctly). In current code base, this
configuration controls whether we could get the full information (include
current and history) for the apps/attempts/containers by using YarnClient. But
the pre-requirement is that we have to run the TimelineServer. If we turn off
the timeline server but enable AHS, it would give the connection exception
because it tries to connect the ATS.
> 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
> 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
