You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by mi...@apache.org on 2014/10/07 05:49:28 UTC

git commit: HBASE-10411 Add a kerberos 'request is a replay (34)' issue in the Troubleshooting chapter (Takeshi Miao)

Repository: hbase
Updated Branches:
  refs/heads/master f80d4ba16 -> b9701d056


HBASE-10411 Add a kerberos 'request is a replay (34)' issue in the Troubleshooting chapter (Takeshi Miao)


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

Branch: refs/heads/master
Commit: b9701d05690acc505580ea9dee167d62986a84e3
Parents: f80d4ba
Author: Misty Stanley-Jones <ms...@cloudera.com>
Authored: Tue Oct 7 13:48:49 2014 +1000
Committer: Misty Stanley-Jones <ms...@cloudera.com>
Committed: Tue Oct 7 13:49:11 2014 +1000

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


http://git-wip-us.apache.org/repos/asf/hbase/blob/b9701d05/src/main/docbkx/troubleshooting.xml
----------------------------------------------------------------------
diff --git a/src/main/docbkx/troubleshooting.xml b/src/main/docbkx/troubleshooting.xml
index 8195cba..c2463b0 100644
--- a/src/main/docbkx/troubleshooting.xml
+++ b/src/main/docbkx/troubleshooting.xml
@@ -662,7 +662,26 @@ java.lang.Thread.State: WAITING (on object monitor)
       <para> For additional information, see this thread on <link
           xlink:href="http://search-hadoop.com/m/WUnLM6ojHm1/Long+client+pauses+with+compression&amp;subj=Long+client+pauses+with+compression">Long
           client pauses with compression</link>. </para>
-
+    </section>
+    <section xml:id="trouble.client.security.rpc.krb">
+      <title>Secure Client Connect ([Caused by GSSException: No valid credentials provided...])</title>
+      <para>You may encounter the following error:</para>
+      <screen>Secure Client Connect ([Caused by GSSException: No valid credentials provided
+        (Mechanism level: Request is a replay (34) V PROCESS_TGS)])</screen>
+      <para> This issue is caused by bugs in the MIT Kerberos replay_cache component, <link
+          xlink:href="http://krbdev.mit.edu/rt/Ticket/Display.html?id=1201">#1201</link> and <link
+          xlink:href="http://krbdev.mit.edu/rt/Ticket/Display.html?id=5924">#5924</link>. These bugs
+        caused the old version of krb5-server to erroneously block subsequent requests sent from a
+        Principal. This caused krb5-server to block the connections sent from one Client (one HTable
+        instance with multi-threading connection instances for each regionserver); Messages, such as
+          <literal>Request is a replay (34)</literal>, are logged in the client log You can ignore
+        the messages, because HTable will retry 5 * 10 (50) times for each failed connection by
+        default. HTable will throw IOException if any connection to the regionserver fails after the
+        retries, so that the user client code for HTable instance can handle it further. </para>
+      <para> Alternatively, update krb5-server to a version which solves these issues, such as
+        krb5-server-1.10.3. See JIRA <link
+          xlink:href="https://issues.apache.org/jira/browse/HBASE-10379">HBASE-10379</link> for more
+        details. </para>
     </section>
     <section
       xml:id="trouble.client.zookeeper">