More around how to set up pseudo-distributed... point at hdfs pseudo-distribute doc for setting it up first

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1390241 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2012-09-26 00:47:53 +00:00
parent 09538d85dc
commit 23e23bf176
1 changed files with 9 additions and 32 deletions

View File

@ -417,15 +417,14 @@ 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>.
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>First, setup your HDFS in <link xlink:href="http://hadoop.apache.org/docs/r1.0.3/single_node_setup.html">pseudo-distributed mode</link>.
</para>
<para>Next, configure HBase for usage. Below is an example <filename>conf/hbase-site.xml</filename>.
<para>Next, configure HBase. 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" />.
Note that the <varname>hbase.rootdir</varname> property points to the local HDFS instance.
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
@ -442,39 +441,16 @@ to ensure well-formedness of your document after an edit session.
HBase (it'll create them if you let it).</para>
</note>
<note>
<para>Above we bind to <varname>localhost</varname>. This means
that a remote client cannot connect.</para>
</note>
<section xml:id="pseudo.config">
<title>Pseudo-distributed Configuration Files</title>
<para>The following are exmaple configuration files from a pseudo-distributed setup.
</para>
<filename>hdfs-site.xml</filename>
<programlisting>
&lt;configuration&gt;
...
&lt;property&gt;
&lt;name&gt;dfs.name.dir&lt;/name&gt;
&lt;value&gt;/Users/local/user.name/hdfs-data-name&lt;/value&gt;
&lt;/property&gt;
&lt;property&gt;
&lt;name&gt;dfs.data.dir&lt;/name&gt;
&lt;value&gt;/Users/local/user.name/hdfs-data&lt;/value&gt;
&lt;/property&gt;
...
&lt;/configuration&gt;
</programlisting>
<title>Pseudo-distributed Configuration File</title>
<para>Below is a sample pseudo-distributed file for the node <varname>h-24-30.example.com</varname>.
<filename>hbase-site.xml</filename>
<programlisting>
&lt;configuration&gt;
...
&lt;property&gt;
&lt;name&gt;hbase.rootdir&lt;/name&gt;
&lt;value&gt;hdfs://localhost:8020/hbase&lt;/value&gt;
&lt;value&gt;hdfs://h-24-30.sfo.stumble.net:8020/hbase&lt;/value&gt;
&lt;/property&gt;
&lt;property&gt;
&lt;name&gt;hbase.cluster.distributed&lt;/name&gt;
@ -482,11 +458,12 @@ to ensure well-formedness of your document after an edit session.
&lt;/property&gt;
&lt;property&gt;
&lt;name&gt;hbase.zookeeper.quorum&lt;/name&gt;
&lt;value&gt;localhost&lt;/value&gt;
&lt;value&gt;h-24-30.sfo.stumble.net&lt;/value&gt;
&lt;/property&gt;
...
&lt;/configuration&gt;
</programlisting>
</para>
</section>