Index: src/docbkx/performance.xml =================================================================== --- src/docbkx/performance.xml (revision 1136708) +++ src/docbkx/performance.xml (working copy) @@ -92,8 +92,8 @@
Compression - Production systems should use compression such as compression with their column family - definitions. + Production systems should use compression with their column family definitions. See for more information. +
Index: src/docbkx/book.xml =================================================================== --- src/docbkx/book.xml (revision 1136708) +++ src/docbkx/book.xml (working copy) @@ -1384,9 +1384,19 @@ LZO - - See above. - + 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 Using LZO Compression + wiki page for how to make LZO work with HBase. + + 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. + See + for a feature to help protect against failed LZO install.
Index: src/docbkx/troubleshooting.xml =================================================================== --- src/docbkx/troubleshooting.xml (revision 1136708) +++ src/docbkx/troubleshooting.xml (working copy) @@ -482,7 +482,7 @@ at java.lang.Runtime.loadLibrary0(Runtime.java:823) at java.lang.System.loadLibrary(System.java:1028) - .. then there is a path issue with the compression libraries. See the Configuration section on LZO compression configuration. + .. then there is a path issue with the compression libraries. See the Configuration section on LZO compression configuration.
Index: src/docbkx/configuration.xml =================================================================== --- src/docbkx/configuration.xml (revision 1136708) +++ src/docbkx/configuration.xml (working copy) @@ -175,28 +175,12 @@ -
- LZO compression<indexterm><primary>LZO</primary></indexterm> - You should consider enabling LZO compression. Its - near-frictionless and in most all cases boosts performance. - - 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 Using LZO Compression - wiki page for how to make LZO work with HBase. +
+ Compression + 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. - 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 paragraphSee - - for a feature to help protect against failed LZO install. - - See also - at the tail of this book. + See for more information.
Bigger Regions