[
https://issues.apache.org/jira/browse/YARN-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862416#comment-15862416
]
Hudson commented on YARN-6170:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11235 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11235/])
YARN-6170. TimelineReaderServer should wait to join with HttpServer2
(varunsaxena: rev 649deb72fbb62568b4ea0d67444df6faaaed169d)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice/src/main/java/org/apache/hadoop/yarn/server/timelineservice/reader/TimelineReaderServer.java
> TimelineReaderServer should wait to join with HttpServer2
> ---------------------------------------------------------
>
> Key: YARN-6170
> URL: https://issues.apache.org/jira/browse/YARN-6170
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelinereader
> Affects Versions: 3.0.0-alpha2, YARN-5355
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Priority: Minor
> Fix For: YARN-5355-branch-2, 3.0.0-alpha3
>
> Attachments: YARN-6170.01.patch
>
>
> While I was backporting YARN-5355-branch-2 to a 2.6.0-based code branch, I
> noticed that the timeline reader daemon would promptly shut down upon start.
> It turns out that in the 2.6.0 code line at least there are only daemon
> threads left once the main method returns. That causes the JVM to shut down.
> The right pattern to start an embedded jetty web server is to call
> {{Server.start()}} followed by {{Server.join()}}. That way, the server stays
> up reliably no matter what other threads get created.
> It works on YARN-5355 only because there *happens* to be one other non-daemon
> thread. We should add the {{join()}} call to be always correct.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
