[
https://issues.apache.org/jira/browse/YARN-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995404#comment-13995404
]
Hudson commented on YARN-1982:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5603 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5603/])
YARN-1982. Renamed the daemon name to be TimelineServer instead of History
Server and deprecated the old usage. Contributed by Zhijie Shen. (vinodkv:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1593748)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/bin/yarn
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/conf/yarn-env.sh
> Rename the daemon name to timelineserver
> ----------------------------------------
>
> Key: YARN-1982
> URL: https://issues.apache.org/jira/browse/YARN-1982
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Labels: cli
> Fix For: 2.5.0
>
> Attachments: YARN-1982.1.patch
>
>
> Nowadays, it's confusing that we call the new component timeline server, but
> we use
> {code}
> yarn historyserver
> yarn-daemon.sh start historyserver
> {code}
> to start the daemon.
> Before the confusion keeps being propagated, we'd better to modify command
> line asap.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
