[
https://issues.apache.org/jira/browse/MAPREDUCE-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453493#comment-13453493
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-4649:
----------------------------------------------------
bq. On this topic, what is the purpose of mr-jobhistory-daemon ? Is it just for
starting the history server ? If yes, then should we really pass in the command
to start, like
Yes, today it is only for starting the history server. But the script is
generic enough like the rest of the hadoop scripts to start arbitrary command
bq. Can't it just be: mr-jobhistory-daemon.sh start and 'historyserver' is
passed internally ?
Instead I think we should rename it back to a generic mapred-daemon.sh to start
arbitrary mapreduce specific daemons. Can you file a ticket?
> mr-jobhistory-daemon.sh needs to be updated post YARN-1
> -------------------------------------------------------
>
> Key: MAPREDUCE-4649
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4649
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 0.23.3, 2.0.2-alpha
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> Even today, JHS is assuming that YARN_HOME will be same as HADOOP_MAPRED_HOME
> besides other such assumptions. We need to fix it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
