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 (JIRA)" <ji...@apache.org> on 2011/09/22 20:29:26 UTC
[jira] [Created] (BIGTOP-105) hadoop services can not be started
with the default configs in place
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>
hdfs-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
[jira] [Updated] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-105:
------------------------------------
Fix Version/s: (was: 0.3.0)
0.4.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.4.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
[jira] [Updated] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112953#comment-13112953 ]
Roman Shaposhnik commented on BIGTOP-105:
-----------------------------------------
Those instructions seem to be pretty outdated by now. However, there seems to be a relevant JIRA: HADOOP-7673
> 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
[jira] [Commented] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112840#comment-13112840 ]
Roman Shaposhnik commented on BIGTOP-105:
-----------------------------------------
Eli, what's the proper way of generating a tarball with configs (IOW, a thing that would later become an Apache release of Hadoop .23)? I tried this:
$ mvn package -DskipTests -Pdist -Dtar
and the resulting tarball didn't have much configs at all:
$ $ tar tvf ./hadoop-common-project/hadoop-common/target/hadoop-common-0.24.0-SNAPSHOT.tar.gz| fgrep "/etc"
drwxr-xr-x rvs/rvs 0 2011-09-22 11:59 hadoop-common-0.24.0-SNAPSHOT/etc/
drwxr-xr-x rvs/rvs 0 2011-09-22 11:59 hadoop-common-0.24.0-SNAPSHOT/etc/hadoop/
-rw-r--r-- rvs/rvs 2301 2011-09-22 11:59 hadoop-common-0.24.0-SNAPSHOT/etc/hadoop/hadoop-metrics.properties
-rw-r--r-- rvs/rvs 2376 2011-09-22 11:59 hadoop-common-0.24.0-SNAPSHOT/etc/hadoop/hadoop-metrics2.properties
-rw-r--r-- rvs/rvs 1243 2011-09-22 11:59 hadoop-common-0.24.0-SNAPSHOT/etc/hadoop/ssl-client.xml.example
-rw-r--r-- rvs/rvs 6354 2011-09-22 11:59 hadoop-common-0.24.0-SNAPSHOT/etc/hadoop/log4j.properties
-rw-r--r-- rvs/rvs 1195 2011-09-22 11:59 hadoop-common-0.24.0-SNAPSHOT/etc/hadoop/ssl-server.xml.example
> 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
[jira] [Updated] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ 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
> 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
>
>
> 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
[jira] [Commented] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112818#comment-13112818 ]
Eli Collins commented on BIGTOP-105:
------------------------------------
It's worth looking into what's done upstream in src/packages so the conf is similar (see hadoop-setup-conf).
> 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
[jira] [Updated] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-105:
------------------------------------
Description:
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
was:
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>
hdfs-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
> 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
[jira] [Commented] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Bruno Mahé (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138868#comment-13138868 ]
Bruno Mahé commented on BIGTOP-105:
-----------------------------------
+1
> 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
[jira] [Commented] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112907#comment-13112907 ]
Patrick Hunt commented on BIGTOP-105:
-------------------------------------
FYI some details here I would think: http://wiki.apache.org/hadoop/HowToRelease
> 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
[jira] [Updated] (BIGTOP-105) hadoop services can not be started
with the default configs in place
Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-105:
------------------------------------
Fix Version/s: (was: 0.2.0)
0.3.0
Now that the workaround is in place -- pushing the real fix out to 0.3.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.3.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