[
https://issues.apache.org/jira/browse/BIGTOP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112810#comment-13112810
]
Roman Shaposhnik commented on BIGTOP-105:
-----------------------------------------
An alternative would be to make upstream hadoop have reasonable defaults so
that services can be started with empty configs.
> 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
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
