You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2009/11/24 21:01:39 UTC

[jira] Updated: (HBASE-2009) [EC2] support mapreduce subsystem

     [ https://issues.apache.org/jira/browse/HBASE-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-2009:
----------------------------------

      Description: 
Feedback up on hbase-user@ from Naresh Rapolu:

{quote}
    Your scripts are working fine. We restarted everything and tested, and they are working fine. A few issues though :

        * While starting, launch-hbase-cluster gives the following error.
          error: "fs.epoll.max_user_instance" is an unknown key. It occurs during starting zookeeper instances.
        * We needed MapReduce along with HBase. The note on the JIRA page that you only need to add only two lines in hbase-ec2-env.sh is insufficient.
          The following changes need to be made.
          1. hbase-ec2-env.sh should write mapred.job.tracker property into hadoop-site.xml ( Also shouldnt you be having core-site.xml and hdfs-site.xml as it is hadoop-0.20.1 ??? Infact because of this , there are warning messages all over the place when you are using hdfs through command line ).
          2. HADOOP_CLASSPATH in hadoop/conf/hadoop-env.sh needs to be changed in the underlying AMI, to include hbase, zookeeper jars and conf directory. Probably you can modify the public AMI, and recreate the bundle as the paths to these are known apriori. 3. For other users, the following three lines should be added in hbase-ec2-env.sh
          For master:
          "$HADOOP_HOME"/bin/hadoop-daemon.sh start jobtracker
          "$HADOOP_HOME"/bin/hadoop-daemon.sh start tasktracker
          For slave:
          "$HADOOP_HOME"/bin/hadoop-daemon.sh start tasktracker.
{quote}

         Priority: Minor  (was: Major)
    Fix Version/s: 0.21.0
                   0.20.3

> [EC2] support mapreduce subsystem
> ---------------------------------
>
>                 Key: HBASE-2009
>                 URL: https://issues.apache.org/jira/browse/HBASE-2009
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Minor
>             Fix For: 0.20.3, 0.21.0
>
>
> Feedback up on hbase-user@ from Naresh Rapolu:
> {quote}
>     Your scripts are working fine. We restarted everything and tested, and they are working fine. A few issues though :
>         * While starting, launch-hbase-cluster gives the following error.
>           error: "fs.epoll.max_user_instance" is an unknown key. It occurs during starting zookeeper instances.
>         * We needed MapReduce along with HBase. The note on the JIRA page that you only need to add only two lines in hbase-ec2-env.sh is insufficient.
>           The following changes need to be made.
>           1. hbase-ec2-env.sh should write mapred.job.tracker property into hadoop-site.xml ( Also shouldnt you be having core-site.xml and hdfs-site.xml as it is hadoop-0.20.1 ??? Infact because of this , there are warning messages all over the place when you are using hdfs through command line ).
>           2. HADOOP_CLASSPATH in hadoop/conf/hadoop-env.sh needs to be changed in the underlying AMI, to include hbase, zookeeper jars and conf directory. Probably you can modify the public AMI, and recreate the bundle as the paths to these are known apriori. 3. For other users, the following three lines should be added in hbase-ec2-env.sh
>           For master:
>           "$HADOOP_HOME"/bin/hadoop-daemon.sh start jobtracker
>           "$HADOOP_HOME"/bin/hadoop-daemon.sh start tasktracker
>           For slave:
>           "$HADOOP_HOME"/bin/hadoop-daemon.sh start tasktracker.
> {quote}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.