Add troubleshooting on hbase dfsclient1 connection to h2, also edit of pseudo-distributed section... needs more work
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1389527 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
66146c49d6
commit
e343aae374
|
@ -417,14 +417,15 @@ to ensure well-formedness of your document after an edit session.
|
|||
HBase. Do not use this configuration for production nor for
|
||||
evaluating HBase performance.</para>
|
||||
|
||||
<para>First, confirm your local HDFS setup. Below is an example <filename>conf/hdfs-site.xml</filename>. Note
|
||||
that the replication is set to 1 because this is a pseudo-distributed setup. The properties <varname>dfs.name.dir</varname>
|
||||
and <varname>dfs.data.dir</varname> are being set explicitly, the latter being where HDFS data will exist on your machine.
|
||||
</para>
|
||||
<para>Next, configure HBase for usage. Below is an example <filename>conf/hbase-site.xml</filename>. Note
|
||||
that the <varname>hbase.rootdir</varname> property points to the local HDFS instance. This is the file into
|
||||
<para>First, confirm your local HDFS setup. Below is an example <filename>conf/hdfs-site.xml</filename>.
|
||||
The properties <varname>dfs.name.dir</varname> and <varname>dfs.data.dir</varname> are being set explicitly,
|
||||
the latter being where HDFS data will exist on your machine.
|
||||
</para>
|
||||
<para>Next, configure HBase for usage. Below is an example <filename>conf/hbase-site.xml</filename>.
|
||||
This is the file into
|
||||
which you add local customizations and overrides for
|
||||
<xref linkend="hbase_default_configurations" /> and <xref linkend="hdfs_client_conf" />
|
||||
<xref linkend="hbase_default_configurations" /> and <xref linkend="hdfs_client_conf" />.
|
||||
Note that the <varname>hbase.rootdir</varname> property points to the local HDFS instance.
|
||||
</para>
|
||||
|
||||
<para>Now skip to <xref linkend="confirm" /> for how to start and verify your
|
||||
|
@ -443,8 +444,7 @@ to ensure well-formedness of your document after an edit session.
|
|||
|
||||
<note>
|
||||
<para>Above we bind to <varname>localhost</varname>. This means
|
||||
that a remote client cannot connect. Amend accordingly, if you
|
||||
want to connect from a remote location.</para>
|
||||
that a remote client cannot connect.</para>
|
||||
</note>
|
||||
|
||||
|
||||
|
@ -464,10 +464,6 @@ to ensure well-formedness of your document after an edit session.
|
|||
<name>dfs.data.dir</name>
|
||||
<value>/Users/local/user.name/hdfs-data</value>
|
||||
</property>
|
||||
<property>
|
||||
<name>dfs.replication</name>
|
||||
<value>1</value>
|
||||
</property>
|
||||
...
|
||||
</configuration>
|
||||
</programlisting>
|
||||
|
@ -480,14 +476,14 @@ to ensure well-formedness of your document after an edit session.
|
|||
<name>hbase.rootdir</name>
|
||||
<value>hdfs://localhost:8020/hbase</value>
|
||||
</property>
|
||||
<property>
|
||||
<name>hbase.zookeeper.quorum</name>
|
||||
<value>localhost</value>
|
||||
</property>
|
||||
<property>
|
||||
<name>hbase.cluster.distributed</name>
|
||||
<value>true</value>
|
||||
</property>
|
||||
<property>
|
||||
<name>hbase.zookeeper.quorum</name>
|
||||
<value>localhost</value>
|
||||
</property>
|
||||
...
|
||||
</configuration>
|
||||
</programlisting>
|
||||
|
|
|
@ -1059,6 +1059,19 @@ you need to copy under <filename>hbase/lib</filename>, the <filename>commons-con
|
|||
in your Hadoop's <filename>lib</filename> directory. That should fix the above complaint.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section xml:id="trouble.versions.205">
|
||||
<title>...cannot communicate with client version...</title>
|
||||
<para>If you see something like the following in your logs
|
||||
<computeroutput>...
|
||||
2012-09-24 10:20:52,168 FATAL org.apache.hadoop.hbase.master.HMaster: Unhandled exception. Starting shutdown.
|
||||
org.apache.hadoop.ipc.RemoteException: Server IPC version 7 cannot communicate with client version 4
|
||||
...</computeroutput>
|
||||
...are you trying to talk to an Hadoop 2.0.x from an HBase that has an Hadoop 1.0.x client?
|
||||
Use the HBase built against Hadoop 2.0 or rebuild your HBase passing the <command>-Dhadoop.profile=2.0</command>
|
||||
attribute to Maven (See <xref linkend="maven.build.hadoop" /> for more).
|
||||
</para>
|
||||
|
||||
</section>
|
||||
|
||||
<section xml:id="trouble.casestudy">
|
||||
|
|
Loading…
Reference in New Issue