[
https://issues.apache.org/jira/browse/YARN-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157686#comment-16157686
]
Hudson commented on YARN-7152:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #12811 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/12811/])
YARN-7152. [ATSv2] Registering timeline client before AMRMClient service
(varunsaxena: rev ef87d34a0e96f6b6390b7086c4ea2d5b7a4c2754)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/api/AMRMClient.java
> [ATSv2] Registering timeline client before AMRMClient service init throw
> exception.
> ------------------------------------------------------------------------------------
>
> Key: YARN-7152
> URL: https://issues.apache.org/jira/browse/YARN-7152
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineclient
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Fix For: 3.0.0-beta1, YARN-5355_branch2, 3.1.0
>
> Attachments: YARN-7152.01.patch, YARN-7152.02.patch
>
>
> It is observed that registering timeline v2 client with AMRMClient before
> serviceInit throw exception in AppMaster. This causes AppMaster start up
> failure.
> {noformat}
> Caused by: org.apache.hadoop.yarn.exceptions.YarnException: register timeline
> v2 client when not configured.
> at
> org.apache.hadoop.yarn.client.api.AMRMClient.registerTimelineV2Client(AMRMClient.java:708)
> at
> org.apache.hadoop.yarn.client.api.async.AMRMClientAsync.registerTimelineV2Client(AMRMClientAsync.java:354)
> {noformat}
> AMRMClient should not assume that timeline client will be registered only
> after serviceInit. In composite service model, this will be a issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
