Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-3998 book.xml / configuration.xml - reorganize LZO compression info 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1138308 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2011-06-22 05:31:44 +00:00
parent d6a24bcf96
commit ad82eefcd0
4 changed files with 21 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
src/docbkx/book.xml
View File

@ -1384,9 +1384,19 @@ false
<title>
LZO
</title>
<para>
See <xref linkend="lzo" /> above.
<para>Unfortunately, HBase cannot ship with LZO because of
the licensing issues; HBase is Apache-licensed, LZO is GPL.
Therefore LZO install is to be done post-HBase install.
See the <link xlink:href="http://wiki.apache.org/hadoop/UsingLzoCompression">Using LZO Compression</link>
wiki page for how to make LZO work with HBase.
</para>
<para>A common problem users run into when using LZO is that while initial
setup of the cluster runs smooth, a month goes by and some sysadmin goes to
add a machine to the cluster only they'll have forgotten to do the LZO
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. </para>
<para>See <xref linkend="hbase.regionserver.codecs" />
for a feature to help protect against failed LZO install.</para>
</section>
<section xml:id="gzip.compression">

26
src/docbkx/configuration.xml
View File

@ -175,28 +175,12 @@ to ensure well-formedness of your document after an edit session.
</section>
<section xml:id="lzo">
<title>LZO compression<indexterm><primary>LZO</primary></indexterm></title>
<para>You should consider enabling LZO compression. Its
near-frictionless and in most all cases boosts performance.
<section xml:id="config.compression">
<title>Compression</title>
<para>You should consider enabling ColumnFamily compression. There are several options that are near-frictionless and in most all cases boost
performance by reducing the size of StoreFiles and thus reducing I/O.
</para>
<para>Unfortunately, HBase cannot ship with LZO because of
the licensing issues; HBase is Apache-licensed, LZO is GPL.
Therefore LZO install is to be done post-HBase install.
See the <link xlink:href="http://wiki.apache.org/hadoop/UsingLzoCompression">Using LZO Compression</link>
wiki page for how to make LZO work with HBase.
</para>
<para>A common problem users run into when using LZO is that while initial
setup of the cluster runs smooth, a month goes by and some sysadmin goes to
add a machine to the cluster only they'll have forgotten to do the LZO
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
<xref linkend="hbase.regionserver.codecs" />
for a feature to help protect against failed LZO install</para></footnote>.
</para>
<para>See also <xref linkend="compression" />
at the tail of this book.</para>
<para>See <xref linkend="compression" /> for more information.</para>
</section>
<section xml:id="bigger.regions">
<title>Bigger Regions</title>

4
src/docbkx/performance.xml
View File

@ -92,8 +92,8 @@
<section xml:id="perf.compression">
<title>Compression</title>
<para>Production systems should use compression such as <xref linkend="lzo" /> compression with their column family
definitions.</para>
<para>Production systems should use compression with their column family definitions. See <xref linkend="compression" /> for more information.
</para>
</section>
<section xml:id="perf.handlers">

2
src/docbkx/troubleshooting.xml
View File

@ -508,7 +508,7 @@ java.lang.UnsatisfiedLinkError: no gplcompression in java.library.path
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1028)
</programlisting>
.. then there is a path issue with the compression libraries. See the Configuration section on <link linkend="lzo">LZO compression configuration</link>.
.. then there is a path issue with the compression libraries. See the Configuration section on <link linkend="lzo.compression">LZO compression configuration</link>.
</para>
</section>
</section>