From 34c8e0ab16811cc1764940b9a14b0dce3050a078 Mon Sep 17 00:00:00 2001 From: Michael Stack Date: Fri, 2 Aug 2013 19:01:34 +0000 Subject: [PATCH] HBASE-8224 Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1509813 13f79535-47bb-0310-9956-ffa450edef68 --- hbase-client/pom.xml | 19 +++- hbase-common/pom.xml | 40 ++++--- .../org/apache/hadoop/hbase/util/JVM.java | 10 +- hbase-examples/pom.xml | 45 +++++--- hbase-hadoop1-compat/pom.xml | 8 +- hbase-hadoop2-compat/pom.xml | 18 ++- hbase-it/pom.xml | 53 ++++++++- hbase-prefix-tree/pom.xml | 99 ++++++++++++++++ hbase-server/pom.xml | 53 +++++++-- .../hadoop/hbase/constraint/package-info.java | 106 +++++++++--------- .../thrift/HThreadedSelectorServerArgs.java | 8 +- .../hbase/master/TestMasterNoCluster.java | 8 +- pom.xml | 101 +++++++++++++---- 13 files changed, 418 insertions(+), 150 deletions(-) diff --git a/hbase-client/pom.xml b/hbase-client/pom.xml index 7d5e413a24b..3ddf2ae71de 100644 --- a/hbase-client/pom.xml +++ b/hbase-client/pom.xml @@ -154,10 +154,11 @@ activation property as the parent Hadoop 1.0.x profile to make sure it gets run at the same time. --> - hadoop-1.0 + hadoop-1.1 - !hadoop.profile + + !hadoop.profile @@ -176,14 +177,22 @@ hadoop-2.0 - hadoop.profile - 2.0 + + hadoop.profile2.0 org.apache.hadoop - hadoop-client + hadoop-common + + + org.apache.hadoop + hadoop-auth + + + org.apache.hadoop + hadoop-mapreduce-client-core org.apache.hadoop diff --git a/hbase-common/pom.xml b/hbase-common/pom.xml index 05093d9ac3d..e0002656583 100644 --- a/hbase-common/pom.xml +++ b/hbase-common/pom.xml @@ -187,14 +187,27 @@ commons-logging commons-logging - - org.slf4j - slf4j-api - - - org.slf4j - slf4j-log4j12 - + + commons-codec + commons-codec + compile + + + commons-lang + commons-lang + compile + + + commons-collections + commons-collections + 3.2.1 + compile + + + commons-io + commons-io + compile + @@ -218,7 +231,8 @@ hadoop-1.1 - !hadoop.profile + + !hadoop.profile @@ -260,18 +274,18 @@ hadoop-2.0 - hadoop.profile - 2.0 + + hadoop.profile2.0 org.apache.hadoop - hadoop-client + hadoop-annotations org.apache.hadoop - hadoop-annotations + hadoop-common diff --git a/hbase-common/src/main/java/org/apache/hadoop/hbase/util/JVM.java b/hbase-common/src/main/java/org/apache/hadoop/hbase/util/JVM.java index d91c8b2eee6..a60d96c51c9 100644 --- a/hbase-common/src/main/java/org/apache/hadoop/hbase/util/JVM.java +++ b/hbase-common/src/main/java/org/apache/hadoop/hbase/util/JVM.java @@ -27,10 +27,10 @@ import java.io.IOException; import java.io.InputStream; import java.io.InputStreamReader; -import org.slf4j.Logger; -import org.slf4j.LoggerFactory; import java.lang.reflect.Method; +import org.apache.commons.logging.Log; +import org.apache.commons.logging.LogFactory; import org.apache.hadoop.classification.InterfaceAudience; import org.apache.hadoop.classification.InterfaceStability; @@ -44,10 +44,8 @@ import org.apache.hadoop.classification.InterfaceStability; @InterfaceAudience.Public @InterfaceStability.Evolving -public class JVM -{ - static final Logger LOG = LoggerFactory.getLogger(JVM.class); - +public class JVM { + private static final Log LOG = LogFactory.getLog(JVM.class); private OperatingSystemMXBean osMbean; private static final boolean ibmvendor = diff --git a/hbase-examples/pom.xml b/hbase-examples/pom.xml index e88f77c324c..bb4ba0d9a8c 100644 --- a/hbase-examples/pom.xml +++ b/hbase-examples/pom.xml @@ -63,12 +63,34 @@ + + org.apache.hbase + hbase-common + org.apache.hbase hbase-common test-jar test + + org.apache.hbase + hbase-protocol + compile + + + org.apache.hbase + hbase-client + compile + + + org.apache.zookeeper + zookeeper + + + com.google.protobuf + protobuf-java + org.apache.hbase hbase-server @@ -84,12 +106,8 @@ libthrift - org.slf4j - slf4j-api - - - org.slf4j - slf4j-log4j12 + commons-logging + commons-logging @@ -117,7 +135,8 @@ if we can combine these profiles somehow --> hadoop-1.1 - !hadoop.profile + + !hadoop.profile @@ -139,22 +158,18 @@ if we can combine these profiles somehow --> hadoop-2.0 - hadoop.profile - 2.0 + + hadoop.profile2.0 org.apache.hadoop - hadoop-client + hadoop-mapreduce-client-core org.apache.hadoop - hadoop-annotations - - - org.apache.hadoop - hadoop-minicluster + hadoop-common diff --git a/hbase-hadoop1-compat/pom.xml b/hbase-hadoop1-compat/pom.xml index d24a5d12a76..f5f2c34f67f 100644 --- a/hbase-hadoop1-compat/pom.xml +++ b/hbase-hadoop1-compat/pom.xml @@ -117,10 +117,6 @@ limitations under the License. com.yammer.metrics metrics-core - - log4j - log4j - org.apache.hadoop hadoop-test @@ -128,6 +124,10 @@ limitations under the License. true test + + commons-logging + commons-logging + diff --git a/hbase-hadoop2-compat/pom.xml b/hbase-hadoop2-compat/pom.xml index c1d1fa23df3..a30f45999c3 100644 --- a/hbase-hadoop2-compat/pom.xml +++ b/hbase-hadoop2-compat/pom.xml @@ -140,7 +140,7 @@ limitations under the License. org.apache.hadoop - hadoop-client + hadoop-mapreduce-client-core ${hadoop-two.version} @@ -157,10 +157,6 @@ limitations under the License. com.yammer.metrics metrics-core - - log4j - log4j - @@ -168,6 +164,18 @@ limitations under the License. hadoop-minicluster ${hadoop-two.version} + + commons-lang + commons-lang + + + commons-logging + commons-logging + + + com.google.guava + guava + diff --git a/hbase-it/pom.xml b/hbase-it/pom.xml index eb3d068255c..8a535d50b01 100644 --- a/hbase-it/pom.xml +++ b/hbase-it/pom.xml @@ -137,11 +137,44 @@ + + org.apache.hbase + hbase-common + jar + org.apache.hbase hbase-common test-jar + + org.apache.hbase + hbase-protocol + + + org.apache.hbase + hbase-client + + + com.google.guava + guava + + + commons-logging + commons-logging + + + commons-cli + commons-cli + + + org.apache.commons + commons-math + + + commons-lang + commons-lang + org.apache.hbase hbase-server @@ -175,6 +208,10 @@ test-jar test + + org.cloudera.htrace + htrace + @@ -200,7 +237,8 @@ hadoop-1.1 - !hadoop.profile + + !hadoop.profile @@ -242,14 +280,19 @@ hadoop-2.0 - hadoop.profile - 2.0 + + hadoop.profile2.0 org.apache.hadoop - hadoop-client + hadoop-mapreduce-client-core + + + org.apache.hadoop + hadoop-mapreduce-client-jobclient + test-jar org.apache.hadoop @@ -257,7 +300,7 @@ org.apache.hadoop - hadoop-minicluster + hadoop-common diff --git a/hbase-prefix-tree/pom.xml b/hbase-prefix-tree/pom.xml index b34df17af46..a229f4dc7ca 100644 --- a/hbase-prefix-tree/pom.xml +++ b/hbase-prefix-tree/pom.xml @@ -78,6 +78,105 @@ org.apache.hbase hbase-common + + org.apache.hbase + hbase-hadoop-compat + + + org.apache.hbase + ${compat.module} + ${project.version} + + + com.google.guava + guava + + + commons-logging + commons-logging + + + + + hadoop-1.1 + + + + !hadoop.profile + + + + + org.apache.hadoop + hadoop-core + + + + + hadoop-1.0 + + + hadoop.profile + 1.0 + + + + + org.apache.hadoop + hadoop-core + + + + + + hadoop-2.0 + + + + hadoop.profile2.0 + + + + + org.apache.hadoop + hadoop-common + + + org.apache.hadoop + hadoop-annotations + + + + + + hadoop-3.0 + + + hadoop.profile + 3.0 + + + + 3.0-SNAPSHOT + + + + org.apache.hadoop + hadoop-common + + + org.apache.hadoop + hadoop-annotations + + + + diff --git a/hbase-server/pom.xml b/hbase-server/pom.xml index 04fd90c6cd0..3d3396804ca 100644 --- a/hbase-server/pom.xml +++ b/hbase-server/pom.xml @@ -299,6 +299,14 @@ hbase-common test-jar + + commons-httpclient + commons-httpclient + + + commons-collections + commons-collections + org.apache.hbase hbase-hadoop-compat @@ -371,6 +379,10 @@ org.apache.zookeeper zookeeper + + org.slf4j + slf4j-api + org.apache.thrift libthrift @@ -419,14 +431,6 @@ org.codehaus.jackson jackson-xc - - org.slf4j - slf4j-api - - - org.slf4j - slf4j-log4j12 - tomcat jasper-compiler @@ -548,7 +552,8 @@ hadoop-1.1 - !hadoop.profile + + !hadoop.profile @@ -589,11 +594,37 @@ hadoop-2.0 - hadoop.profile - 2.0 + + hadoop.profile2.0 + + org.apache.hadoop + hadoop-common + + + org.apache.hadoop + hadoop-auth + + + org.apache.hadoop + hadoop-mapreduce-client-core + + + org.apache.hadoop + hadoop-mapreduce-client-jobclient + test-jar + + + org.apache.hadoop + hadoop-hdfs + + + org.apache.hadoop + hadoop-hdfs + test-jar + org.apache.hadoop hadoop-client diff --git a/hbase-server/src/main/java/org/apache/hadoop/hbase/constraint/package-info.java b/hbase-server/src/main/java/org/apache/hadoop/hbase/constraint/package-info.java index 860fff962d8..9bffc5ccef3 100644 --- a/hbase-server/src/main/java/org/apache/hadoop/hbase/constraint/package-info.java +++ b/hbase-server/src/main/java/org/apache/hadoop/hbase/constraint/package-info.java @@ -18,7 +18,7 @@ /** * Restrict the domain of a data attribute, often times to fulfill business rules/requirements. - * + *

Table of Contents

    @@ -30,94 +30,94 @@

    Overview

    - Constraints are used to enforce business rules in a database. - By checking all {@link org.apache.hadoop.hbase.client.Put Puts} on a given table, you can enforce very specific data policies. - For instance, you can ensure that a certain column family-column qualifier pair always has a value between 1 and 10. + Constraints are used to enforce business rules in a database. + By checking all {@link org.apache.hadoop.hbase.client.Put Puts} on a given table, you can enforce very specific data policies. + For instance, you can ensure that a certain column family-column qualifier pair always has a value between 1 and 10. Otherwise, the {@link org.apache.hadoop.hbase.client.Put} is rejected and the data integrity is maintained.

    - Constraints are designed to be configurable, so a constraint can be used across different tables, but implement different + Constraints are designed to be configurable, so a constraint can be used across different tables, but implement different behavior depending on the specific configuration given to that constraint.

    - By adding a constraint to a table (see Example Usage), constraints will automatically enabled. - You also then have the option of to disable (just 'turn off') or remove (delete all associated information) all constraints on a table. - If you remove all constraints - (see {@link org.apache.hadoop.hbase.constraint.Constraints#remove(org.apache.hadoop.hbase.HTableDescriptor)}, - you must re-add any {@link org.apache.hadoop.hbase.constraint.Constraint} you want on that table. - However, if they are just disabled (see {@link org.apache.hadoop.hbase.constraint.Constraints#disable(org.apache.hadoop.hbase.HTableDescriptor)}, + By adding a constraint to a table (see Example Usage), constraints will automatically enabled. + You also then have the option of to disable (just 'turn off') or remove (delete all associated information) all constraints on a table. + If you remove all constraints + (see {@link org.apache.hadoop.hbase.constraint.Constraints#remove(org.apache.hadoop.hbase.HTableDescriptor)}, + you must re-add any {@link org.apache.hadoop.hbase.constraint.Constraint} you want on that table. + However, if they are just disabled (see {@link org.apache.hadoop.hbase.constraint.Constraints#disable(org.apache.hadoop.hbase.HTableDescriptor)}, all you need to do is enable constraints again, and everything will be turned back on as it was configured. Individual constraints can also be individually enabled, disabled or removed without affecting other constraints.

    - By default, constraints are disabled on a table. + By default, constraints are disabled on a table. This means you will not see any slow down on a table if constraints are not enabled.

    Concurrency and Atomicity

    - Currently, no attempts at enforcing correctness in a multi-threaded scenario when modifying a constraint, via - {@link org.apache.hadoop.hbase.constraint.Constraints}, to the the {@link org.apache.hadoop.hbase.HTableDescriptor}. - This is particularly important when adding a constraint(s) to the {@link org.apache.hadoop.hbase.HTableDescriptor} + Currently, no attempts at enforcing correctness in a multi-threaded scenario when modifying a constraint, via + {@link org.apache.hadoop.hbase.constraint.Constraints}, to the the {@link org.apache.hadoop.hbase.HTableDescriptor}. + This is particularly important when adding a constraint(s) to the {@link org.apache.hadoop.hbase.HTableDescriptor} as it first retrieves the next priority from a custom value set in the descriptor, - adds each constraint (with increasing priority) to the descriptor, and then the next available priority is re-stored - back in the {@link org.apache.hadoop.hbase.HTableDescriptor}. + adds each constraint (with increasing priority) to the descriptor, and then the next available priority is re-stored + back in the {@link org.apache.hadoop.hbase.HTableDescriptor}.

    - Locking is recommended around each of Constraints add methods: - {@link org.apache.hadoop.hbase.constraint.Constraints#add(org.apache.hadoop.hbase.HTableDescriptor, Class...)}, - {@link org.apache.hadoop.hbase.constraint.Constraints#add(org.apache.hadoop.hbase.HTableDescriptor, org.apache.hadoop.hbase.util.Pair...)}, + Locking is recommended around each of Constraints add methods: + {@link org.apache.hadoop.hbase.constraint.Constraints#add(org.apache.hadoop.hbase.HTableDescriptor, Class...)}, + {@link org.apache.hadoop.hbase.constraint.Constraints#add(org.apache.hadoop.hbase.HTableDescriptor, org.apache.hadoop.hbase.util.Pair...)}, and {@link org.apache.hadoop.hbase.constraint.Constraints#add(org.apache.hadoop.hbase.HTableDescriptor, Class, org.apache.hadoop.conf.Configuration)}. Any changes on a single HTableDescriptor should be serialized, either within a single thread or via external mechanisms.

    - Note that having a higher priority means that a constraint will run later; e.g. a constraint with priority 1 will run before a - constraint with priority 2. + Note that having a higher priority means that a constraint will run later; e.g. a constraint with priority 1 will run before a + constraint with priority 2.

    - Since Constraints currently are designed to just implement simple checks (e.g. is the value in the right range), there will - be no atomicity conflicts. - Even if one of the puts finishes the constraint first, the single row will not be corrupted and the 'fastest' write will win; + Since Constraints currently are designed to just implement simple checks (e.g. is the value in the right range), there will + be no atomicity conflicts. + Even if one of the puts finishes the constraint first, the single row will not be corrupted and the 'fastest' write will win; the underlying region takes care of breaking the tie and ensuring that writes get serialized to the table. - So yes, this doesn't ensure that we are going to get specific ordering or even a fully consistent view of the underlying data. + So yes, this doesn't ensure that we are going to get specific ordering or even a fully consistent view of the underlying data.

    Each constraint should only use local/instance variables, unless doing more advanced usage. Static variables could cause difficulties when checking concurrent writes to the same region, leading to either highly locked situations (decreasing through-put) or higher probability of errors. However, as long as each constraint just uses local variables, each thread interacting with the constraint will execute correctly and efficiently.

    Caveats

    - In traditional (SQL) databases, Constraints are often used to enforce referential integrity. - However, in HBase, this will likely cause significant overhead and dramatically decrease the number of - {@link org.apache.hadoop.hbase.client.Put Puts}/second possible on a table. This is because to check the referential integrity + In traditional (SQL) databases, Constraints are often used to enforce referential integrity. + However, in HBase, this will likely cause significant overhead and dramatically decrease the number of + {@link org.apache.hadoop.hbase.client.Put Puts}/second possible on a table. This is because to check the referential integrity when making a {@link org.apache.hadoop.hbase.client.Put}, one must block on a scan for the 'remote' table, checking for the valid reference. - For millions of {@link org.apache.hadoop.hbase.client.Put Puts} a second, this will breakdown very quickly. + For millions of {@link org.apache.hadoop.hbase.client.Put Puts} a second, this will breakdown very quickly. There are several options around the blocking behavior including, but not limited to:
      -
    • Create a 'pre-join' table where the keys are already denormalized
      • +
    • Create a 'pre-join' table where the keys are already denormalized
    • Designing for 'incorrect' references
    • Using an external enforcement mechanism
    There are also several general considerations that must be taken into account, when using Constraints:
      -
    1. All changes made via {@link org.apache.hadoop.hbase.constraint.Constraints} will make modifications to the - {@link org.apache.hadoop.hbase.HTableDescriptor} for a given table. As such, the usual renabling of tables should be used for +
    2. All changes made via {@link org.apache.hadoop.hbase.constraint.Constraints} will make modifications to the + {@link org.apache.hadoop.hbase.HTableDescriptor} for a given table. As such, the usual renabling of tables should be used for propagating changes to the table. When at all possible, Constraints should be added to the table before the table is created.
      3. -
    3. Constraints are run in the order that they are added to a table. This has implications for what order constraints should +
    4. Constraints are run in the order that they are added to a table. This has implications for what order constraints should be added to a table.
      5. -
    5. Whenever new Constraint jars are added to a region server, those region servers need to go through a rolling restart to +
    6. Whenever new Constraint jars are added to a region server, those region servers need to go through a rolling restart to make sure that they pick up the new jars and can enable the new constraints.
    7. There are certain keys that are reserved for the Configuration namespace:
      • _ENABLED - used server-side to determine if a constraint should be run
      • _PRIORITY - used server-side to determine what order a constraint should be run
      - If these items are set, they will be respected in the constraint configuration, but they are taken care of by default in when + If these items are set, they will be respected in the constraint configuration, but they are taken care of by default in when adding constraints to an {@link org.apache.hadoop.hbase.HTableDescriptor} via the usual method.
    -

    - Under the hood, constraints are implemented as a Coprocessor (see {@link org.apache.hadoop.hbase.constraint.ConstraintProcessor} +

    + Under the hood, constraints are implemented as a Coprocessor (see {@link org.apache.hadoop.hbase.constraint.ConstraintProcessor} if you are interested).

    Example usage

    - First, you must define a {@link org.apache.hadoop.hbase.constraint.Constraint}. + First, you must define a {@link org.apache.hadoop.hbase.constraint.Constraint}. The best way to do this is to extend {@link org.apache.hadoop.hbase.constraint.BaseConstraint}, which takes care of some of the more mundane details of using a {@link org.apache.hadoop.hbase.constraint.Constraint}.

    - Let's look at one possible implementation of a constraint - an IntegerConstraint(there are also several simple examples in the tests). + Let's look at one possible implementation of a constraint - an IntegerConstraint(there are also several simple examples in the tests). The IntegerConstraint checks to make sure that the value is a String-encoded int. It is really simple to implement this kind of constraint, the only method needs to be implemented is {@link org.apache.hadoop.hbase.constraint.Constraint#check(org.apache.hadoop.hbase.client.Put)}: @@ -141,18 +141,18 @@ } catch (NumberFormatException e) { throw new ConstraintException("Value in Put (" + p + ") was not a String-encoded integer", e); - } } } + } } }

    - Note that all exceptions that you expect to be thrown must be caught and then rethrown as a - {@link org.apache.hadoop.hbase.exceptions.ConstraintException}. This way, you can be sure that a - {@link org.apache.hadoop.hbase.client.Put} fails for an expected reason, rather than for any reason. - For example, an {@link java.lang.OutOfMemoryError} is probably indicative of an inherent problem in + Note that all exceptions that you expect to be thrown must be caught and then rethrown as a + {@link org.apache.hadoop.hbase.constraint.ConstraintException}. This way, you can be sure that a + {@link org.apache.hadoop.hbase.client.Put} fails for an expected reason, rather than for any reason. + For example, an {@link java.lang.OutOfMemoryError} is probably indicative of an inherent problem in the {@link org.apache.hadoop.hbase.constraint.Constraint}, rather than a failed {@link org.apache.hadoop.hbase.client.Put}.

    If an unexpected exception is thrown (for example, any kind of uncaught {@link java.lang.RuntimeException}), - constraint-checking will be 'unloaded' from the regionserver where that error occurred. + constraint-checking will be 'unloaded' from the regionserver where that error occurred. This means no further {@link org.apache.hadoop.hbase.constraint.Constraint Constraints} will be checked on that server until it is reloaded. This is done to ensure the system remains as available as possible. Therefore, be careful when writing your own Constraint. @@ -166,14 +166,14 @@ Constraints.add(desc, IntegerConstraint.class);

    - Once we added the IntegerConstraint, constraints will be enabled on the table (once it is created) and + Once we added the IntegerConstraint, constraints will be enabled on the table (once it is created) and we will always check to make sure that the value is an String-encoded integer. -

    +

    However, suppose we also write our own constraint, MyConstraint.java. - First, you need to make sure this class-files are in the classpath (in a jar) on the regionserver where + First, you need to make sure this class-files are in the classpath (in a jar) on the regionserver where that constraint will be run (this could require a rolling restart on the region server - see Caveats above)

    - Suppose that MyConstraint also uses a Configuration (see {@link org.apache.hadoop.hbase.constraint.Constraint#getConf()}). + Suppose that MyConstraint also uses a Configuration (see {@link org.apache.hadoop.hbase.constraint.Constraint#getConf()}). Then adding MyConstraint looks like this:

    @@ -191,7 +191,7 @@ will be run first, followed by MyConstraint.

    Suppose we realize that the {@link org.apache.hadoop.conf.Configuration} for MyConstraint is actually wrong - when it was added to the table. Note, when it is added to the table, it is not added by reference, + when it was added to the table. Note, when it is added to the table, it is not added by reference, but is instead copied into the {@link org.apache.hadoop.hbase.HTableDescriptor}. Thus, to change the {@link org.apache.hadoop.conf.Configuration} we are using for MyConstraint, we need to do this: @@ -202,7 +202,7 @@ Constraints.setConfiguration(desc, MyConstraint.class, conf);

    - This will overwrite the previous configuration for MyConstraint, but not change the order of the + This will overwrite the previous configuration for MyConstraint, but not change the order of the constraint nor if it is enabled/disabled.

    Note that the same constraint class can be added multiple times to a table without repercussion. @@ -216,7 +216,7 @@

    This just turns off MyConstraint, but retains the position and the configuration associated with MyConstraint. - Now, if we want to re-enable the constraint, its just another one-liner: + Now, if we want to re-enable the constraint, its just another one-liner: 

      Constraints.enable(desc, MyConstraint.class);
diff --git a/hbase-server/src/main/java/org/apache/hadoop/hbase/thrift/HThreadedSelectorServerArgs.java b/hbase-server/src/main/java/org/apache/hadoop/hbase/thrift/HThreadedSelectorServerArgs.java
index f19ec5fae45..8c4ab615bf6 100644
--- a/hbase-server/src/main/java/org/apache/hadoop/hbase/thrift/HThreadedSelectorServerArgs.java
+++ b/hbase-server/src/main/java/org/apache/hadoop/hbase/thrift/HThreadedSelectorServerArgs.java
@@ -19,21 +19,19 @@
 
 package org.apache.hadoop.hbase.thrift;
 
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
 import org.apache.hadoop.classification.InterfaceAudience;
 import org.apache.hadoop.conf.Configuration;
 import org.apache.thrift.server.TThreadedSelectorServer;
 import org.apache.thrift.transport.TNonblockingServerTransport;
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
 
 /**
  * A TThreadedSelectorServer.Args that reads hadoop configuration
  */
 @InterfaceAudience.Private
 public class HThreadedSelectorServerArgs extends TThreadedSelectorServer.Args {
-
-  private static final Logger LOG =
-      LoggerFactory.getLogger(TThreadedSelectorServer.class);
+  private static final Log LOG = LogFactory.getLog(TThreadedSelectorServer.class);
 
   /**
    * Number of selector threads for reading and writing socket
diff --git a/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterNoCluster.java b/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterNoCluster.java
index 8741952a534..423c5c614e9 100644
--- a/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterNoCluster.java
+++ b/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterNoCluster.java
@@ -65,8 +65,8 @@ import org.junit.BeforeClass;
 import org.junit.Test;
 import org.mockito.Mockito;
 import org.junit.experimental.categories.Category;
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
 
 /**
  * Standup the master and fake it to test various aspects of master function.
@@ -78,7 +78,7 @@ import org.slf4j.LoggerFactory;
  */
 @Category(MediumTests.class)
 public class TestMasterNoCluster {
-  private static Logger LOG = LoggerFactory.getLogger(TestMasterNoCluster.class);
+  private static final Log LOG = LogFactory.getLog(TestMasterNoCluster.class);
   private static final HBaseTestingUtility TESTUTIL = new HBaseTestingUtility();
 
   @BeforeClass
@@ -240,7 +240,7 @@ public class TestMasterNoCluster {
    * @throws IOException
    * @throws KeeperException
    * @throws InterruptedException
-   * @throws DeserializationException 
+   * @throws DeserializationException
    * @throws ServiceException
    */
   @Test (timeout=30000)
diff --git a/pom.xml b/pom.xml
index 1a3e7d869cd..92385c0d039 100644
--- a/pom.xml
+++ b/pom.xml
@@ -461,6 +461,7 @@
         
           org.apache.maven.plugins
           maven-release-plugin
+          2.4.1
           
             -Dmaven.test.skip.exec
+            pom.xml
           
         
         
@@ -609,6 +611,9 @@
             
               prepare-package
               
+                  
                 test-jar
               
             
@@ -884,7 +889,9 @@
     2.4
     2.6
     1.1.1
-    2.1
+    2.2
+    3.2.1
+    3.0.1
     2.1.2
     12.0.1
     1.8.8
@@ -896,13 +903,13 @@
     1.6.8
     4.11
     1.50
-    1.4.3
     1.2.17
     1.9.0
     2.4.1
     1.0.1
     0.9.0
     3.4.5
+    1.6.4
     0.0.1-SNAPSHOT
     2.6.3
     2.3.1
@@ -1045,6 +1052,18 @@
         jettison
         ${jettison.version}
       
+      
+        log4j
+        log4j
+        ${log4j.version}
+      
+      
+      
+        org.slf4j
+        slf4j-api
+        ${slf4j.version}
+      
       
         com.yammer.metrics
         metrics-core
@@ -1055,6 +1074,16 @@
         guava
         ${guava.version}
       
+      
+        commons-collections
+        commons-collections
+        ${collections.version}
+      
+      
+        commons-httpclient
+        commons-httpclient
+        ${httpclient.version}
+      
       
         commons-cli
         commons-cli
@@ -1090,11 +1119,6 @@
         commons-math
         ${commons-math.version}
       
-      
-        log4j
-        log4j
-        ${log4j.version}
-      
       
         org.apache.zookeeper
         zookeeper
@@ -1203,16 +1227,6 @@
         jackson-xc
         ${jackson.version}
       
-      
-        org.slf4j
-        slf4j-api
-        ${slf4j.version}
-      
-      
-        org.slf4j
-        slf4j-log4j12
-        ${slf4j.version}
-      
       
         
     
       junit
@@ -1438,7 +1462,8 @@
       hadoop-1.1
       
         
-          !hadoop.profile
+            
+            !hadoop.profile
         
       
       
@@ -1446,7 +1471,6 @@
       
       
         ${hadoop-one.version}
-        1.4.3
         hbase-hadoop1-compat
         src/main/assembly/hadoop-one-compat.xml
       
@@ -1507,7 +1531,6 @@
         1.0.4
         
         ${hadoop.version}
-        1.4.3
         hbase-hadoop1-compat
         src/main/assembly/hadoop-one-compat.xml
       
@@ -1558,8 +1581,8 @@
       hadoop-2.0
       
         
-          hadoop.profile
-          2.0
+            
+            hadoop.profile2.0
         
       
       
@@ -1567,12 +1590,43 @@
       
       
         ${hadoop-two.version}
-        1.6.1
         hbase-hadoop2-compat
         src/main/assembly/hadoop-two-compat.xml
       
       
         
+          
+            org.apache.hadoop
+            hadoop-mapreduce-client-core
+            ${hadoop-two.version}
+          
+          
+            org.apache.hadoop
+            hadoop-mapreduce-client-jobclient
+            ${hadoop-two.version}
+          
+          
+            org.apache.hadoop
+            hadoop-mapreduce-client-jobclient
+            ${hadoop-two.version}
+            test-jar
+          
+          
+            org.apache.hadoop
+            hadoop-hdfs
+            ${hadoop-two.version}
+          
+          
+            org.apache.hadoop
+            hadoop-hdfs
+            ${hadoop-two.version}
+            test-jar
+          
+          
+            org.apache.hadoop
+            hadoop-auth
+            ${hadoop-two.version}
+          
           
             org.apache.hadoop
             hadoop-common
@@ -1625,7 +1679,6 @@
         
       
       
-        1.6.1
         3.0.0-SNAPSHOT