You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jonathan Eagles (Commented) (JIRA)" <ji...@apache.org> on 2011/12/13 22:45:30 UTC
[jira] [Commented] (MAPREDUCE-3354) JobHistoryServer should be
started by bin/mapred and not by bin/yarn
[ https://issues.apache.org/jira/browse/MAPREDUCE-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168756#comment-13168756 ]
Jonathan Eagles commented on MAPREDUCE-3354:
--------------------------------------------
This patch moves historyserver start/stop to bin/mapred from bin/yarn. I have added support scripts bin/start-mapred.sh bin/stop-mapred.sh and bin/mapred-daemon.sh as supporting scripts. All three support scripts are based completely on their yarn counter parts. I have opted at this point not to create corresponding MAPRED_ environment under the assumption that mapreduce always depends on yarn. I have verified that controlling history server from start-mapred.sh, stop-mapred.sh, mapred-daemon.sh, and mapred all work as expected.
> JobHistoryServer should be started by bin/mapred and not by bin/yarn
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3354
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3354
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver, mrv2
> Affects Versions: 0.23.1, 0.24.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Jonathan Eagles
> Priority: Blocker
> Attachments: MAPREDUCE-3354.patch, MAPREDUCE-3354.patch, MAPREDUCE-3354.patch
>
>
> JobHistoryServer belongs to mapreduce land.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira