You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org> on 2011/10/29 00:10:32 UTC
[jira] [Updated] (BIGTOP-105) hadoop services can not be started
with the default configs in place
[ https://issues.apache.org/jira/browse/BIGTOP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-105:
------------------------------------
Attachment: BIGTOP-105.patch.txt
This is, by no means, an actual solution. Just a workaround that we need to put in place in order to unblock Bigtop 0.2.0
> hadoop services can not be started with the default configs in place
> --------------------------------------------------------------------
>
> Key: BIGTOP-105
> URL: https://issues.apache.org/jira/browse/BIGTOP-105
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.1.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.2.0
>
> Attachments: BIGTOP-105.patch.txt, BIGTOP-105.patch.txt
>
>
> All of the services packaged by Bigtop provide some level of default configuration. Hadoop is the only exception where an extra package is needed to make services usable. I would like to change this by:
> 1. Introducing the following snippets into the configs that get shipped with hadoop package by default:
> core-site.xml:
> <property>
> <name>fs.default.name</name>
> <value>hdfs://localhost:8020</value>
> </property>
>
> mapred-site.xml:
> <property>
> <name>mapred.job.tracker</name>
> <value>localhost:8021</value>
> </property>
> 2. move formating of the namenode from hadoop-conf-pseudo into hadoop-namenode package
--
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