Repository: hbase
Updated Branches:
  refs/heads/master 3702b0b44 -> 454389a4b


HBASE-11508 Document changes to IPC config parameters from HBASE-11492 (Misty 
Stanley-Jones)


Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/454389a4
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/454389a4
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/454389a4

Branch: refs/heads/master
Commit: 454389a4b7e63a731c025748a3d595a168d61640
Parents: 3702b0b
Author: Jonathan M Hsieh <[email protected]>
Authored: Mon Aug 18 14:30:59 2014 -0700
Committer: Jonathan M Hsieh <[email protected]>
Committed: Mon Aug 18 14:30:59 2014 -0700

----------------------------------------------------------------------
 src/main/docbkx/troubleshooting.xml | 86 +++++++++++++++++++++++++++++++-
 1 file changed, 85 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hbase/blob/454389a4/src/main/docbkx/troubleshooting.xml
----------------------------------------------------------------------
diff --git a/src/main/docbkx/troubleshooting.xml 
b/src/main/docbkx/troubleshooting.xml
index 4cd4a9e..bdbe8d9 100644
--- a/src/main/docbkx/troubleshooting.xml
+++ b/src/main/docbkx/troubleshooting.xml
@@ -1264,7 +1264,91 @@ sv4r6s38:       at 
org.apache.hadoop.security.UserGroupInformation.ensureInitial
           linkend="maven.build.hadoop" /> for more). </para>
 
     </section>
-
+    </section>
+  <section>
+    <title>IPC Configuration Conflicts with Hadoop</title>
+    <para>If the Hadoop configuration is loaded after the HBase configuration, 
and you have
+      configured custom IPC settings in both HBase and Hadoop, the Hadoop 
values may overwrite the
+      HBase values. There is normally no need to change these settings for 
HBase, so this problem is
+      an edge case. However, <link
+        
xlink:href="https://issues.apache.org/jira/browse/HBASE-11492";>HBASE-11492</link>
 renames
+      these settings for HBase to remove the chance of a conflict. Each of the 
setting names have
+      been prefixed with <literal>hbase.</literal>, as shown in the following 
table. No action is
+      required related to these changes unless you are already experiencing a 
conflict.</para>
+    <para>These changes were backported to HBase 0.98.x and apply to all newer 
versions.</para>
+    <informaltable>
+      <tgroup
+        cols="2">
+        <thead>
+          <row>
+            <entry>Pre-0.98.x</entry>
+            <entry>0.98-x And Newer</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+            
<entry><para><code>ipc.server.listen.queue.size</code></para></entry>
+            
<entry><para><code>hbase.ipc.server.listen.queue.size</code></para></entry>
+          </row>
+          <row>
+            
<entry><para><code>ipc.server.max.callqueue.size</code></para></entry>
+            
<entry><para><code>hbase.ipc.server.max.callqueue.size</code></para></entry>
+          </row>
+          <row>
+            
<entry><para><code>ipc.server.callqueue.handler.factor</code></para></entry>
+            
<entry><para><code>hbase.ipc.server.callqueue.handler.factor</code></para></entry>
+          </row>
+          <row>
+            
<entry><para><code>ipc.server.callqueue.read.share</code></para></entry>
+            
<entry><para><code>hbase.ipc.server.callqueue.read.share</code></para></entry>
+          </row>
+          <row>
+            <entry><para><code>ipc.server.callqueue.type</code></para></entry>
+            
<entry><para><code>hbase.ipc.server.callqueue.type</code></para></entry>
+          </row>
+          <row>
+            
<entry><para><code>ipc.server.queue.max.call.delay</code></para></entry>
+            
<entry><para><code>hbase.ipc.server.queue.max.call.delay</code></para></entry>
+          </row>
+          <row>
+            
<entry><para><code>ipc.server.max.callqueue.length</code></para></entry>
+            
<entry><para><code>hbase.ipc.server.max.callqueue.length</code></para></entry>
+          </row>
+          <row>
+            
<entry><para><code>ipc.server.read.threadpool.size</code></para></entry>
+            
<entry><para><code>hbase.ipc.server.read.threadpool.size</code></para></entry>
+          </row>
+          <row>
+            <entry><para><code>ipc.server.tcpkeepalive</code></para></entry>
+            
<entry><para><code>hbase.ipc.server.tcpkeepalive</code></para></entry>
+          </row>
+          <row>
+            <entry><para><code>ipc.server.tcpnodelay</code></para></entry>
+            
<entry><para><code>hbase.ipc.server.tcpnodelay</code></para></entry>
+          </row>
+          <row>
+            
<entry><para><code>ipc.client.call.purge.timeout</code></para></entry>
+            
<entry><para><code>hbase.ipc.client.call.purge.timeout</code></para></entry>
+          </row>
+          <row>
+            
<entry><para><code>ipc.client.connection.maxidletime</code></para></entry>
+            
<entry><para><code>hbase.ipc.client.connection.maxidletime</code></para></entry>
+          </row>
+          <row>
+            <entry><para><code>ipc.client.idlethreshold</code></para></entry>
+            
<entry><para><code>hbase.ipc.client.idlethreshold</code></para></entry>
+          </row>
+          <row>
+            <entry><para><code>ipc.client.kill.max</code></para></entry>
+            <entry><para><code>hbase.ipc.client.kill.max</code></para></entry>
+          </row>
+          <row>
+            <entry><para><code>ipc.server.scan.vtime.weight 
</code></para></entry>
+            <entry><para><code>hbase.ipc.server.scan.vtime.weight 
</code></para></entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
   </section>
 
   <section>

Reply via email to