From ad82eefcd07c813382f87829d93ca687d17254a6 Mon Sep 17 00:00:00 2001 From: Michael Stack Date: Wed, 22 Jun 2011 05:31:44 +0000 Subject: [PATCH] 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 --- src/docbkx/book.xml | 16 +++++++++++++--- src/docbkx/configuration.xml | 26 +++++--------------------- src/docbkx/performance.xml | 4 ++-- src/docbkx/troubleshooting.xml | 2 +- 4 files changed, 21 insertions(+), 27 deletions(-) diff --git a/src/docbkx/book.xml b/src/docbkx/book.xml index a9e825b15f8..2fa505934f9 100644 --- a/src/docbkx/book.xml +++ b/src/docbkx/book.xml @@ -1384,9 +1384,19 @@ false 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.
diff --git a/src/docbkx/configuration.xml b/src/docbkx/configuration.xml index 8eafcdad276..dcbd11b30ea 100644 --- a/src/docbkx/configuration.xml +++ b/src/docbkx/configuration.xml @@ -175,28 +175,12 @@ to ensure well-formedness of your document after an edit session.
-
- LZO compression<indexterm><primary>LZO</primary></indexterm> - You should consider enabling LZO compression. Its - near-frictionless and in most all cases boosts performance. +
+ 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. - 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. - 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 diff --git a/src/docbkx/performance.xml b/src/docbkx/performance.xml index 61fe96fb2a8..2d8cdddf0cf 100644 --- a/src/docbkx/performance.xml +++ b/src/docbkx/performance.xml @@ -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. +
diff --git a/src/docbkx/troubleshooting.xml b/src/docbkx/troubleshooting.xml index 12957d85486..08ab434d7a0 100644 --- a/src/docbkx/troubleshooting.xml +++ b/src/docbkx/troubleshooting.xml @@ -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) - .. 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.