HBASE-3146 document feature "hbase.regionserver.codecs"

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1041273 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2010-12-02 04:13:07 +00:00
parent 1955d5dfe4
commit 953068adbb
1 changed files with 5 additions and 5 deletions

View File

@ -1036,7 +1036,7 @@ to ensure well-formedness of your document after an edit session.
fixup on the new machine. In versions since HBase 0.90.0, we should
fail in a way that makes it plain what the problem is, but maybe not.
Remember you read this paragraph<footnote><para>See
<link linkend="hbase.regionserver.codec">hbase.regionserver.codec</link>
<link linkend="hbase.regionserver.codecs">hbase.regionserver.codecs</link>
for a feature to help protect against failed LZO install</para></footnote>.
</para>
</section>
@ -1791,22 +1791,22 @@ to ensure well-formedness of your document after an edit session.
</para>
</section>
<section id="hbase.regionserver.codec">
<section id="hbase.regionserver.codecs">
<title>
<varname>
hbase.regionserver.codec
hbase.regionserver.codecs
</varname>
</title>
<para>
To have a RegionServer test a set of codecs and fail-to-start if any
code is missing or misinstalled, add the configuration
<varname>
hbase.regionserver.codec
hbase.regionserver.codecs
</varname>
to your <filename>hbase-site.xml</filename> with a value of
codecs to test on startup. For example if the
<varname>
hbase.regionserver.codec
hbase.regionserver.codecs
</varname> value is <code>lzo,gz</code> and if lzo is not present
or improperly installed, the misconfigured RegionServer will fail
to start.