[
https://issues.apache.org/jira/browse/HBASE-10411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891964#comment-13891964
]
Hadoop QA commented on HBASE-10411:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12627091/HBASE-10411-trunk-v01.patch
against trunk revision .
ATTACHMENT ID: 12627091
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ <title>Secure Client Connect ([Caused by GSSException: No
valid credentials provided (Mechanism level: Request is a replay (34) V
PROCESS_TGS)])</title>
+This issue is caused by the Kerberos bugs for its 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>,
whom were talking about that the old version of krb5-server would
false-positively blocks subsequent requests sent from a Principal.
+In this case, which means that the krb5-server would sometimes block the
connections sent from one Client (one HTable instance with multi-threading
connection instances for each regionserver); You would see such message
'Request is a replay (34)' in your client log if you hit this bug. You can just
ignore this message due to the implementation of HTable will retry 5 * 10 for
each failed connection by default. The HTable will throw IOException if any
connection to regionserver was failed after the retries, therefore, the user
client code for HTable instance still can handle it further.
+Otherwise, you can pick a new version of krb5-server to solve this issue
gracefully. We tested and mitigated this issue in the environment:
hbase-0.94.16 with krb5-server-1.10.3 on RHEL-6.4_GA-x86_64-10-Hourly2 on AWS,
compared to the old environment: HBase-0.94.16 with krb5-server-1.6.1 on
CentOS-5.3. Please refer to JIRA <link
xlink:href="https://issues.apache.org/jira/browse/HBASE-10379";>HBASE-10379</link>
for more details.
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8603//console
This message is automatically generated.
> [Book] Add a kerberos 'request is a replay (34)' issue at troubleshooting
> section
> ---------------------------------------------------------------------------------
>
> Key: HBASE-10411
> URL: https://issues.apache.org/jira/browse/HBASE-10411
> Project: HBase
> Issue Type: Improvement
> Components: documentation, security
> Reporter: takeshi.miao
> Assignee: takeshi.miao
> Priority: Minor
> Attachments: HBASE-10411-trunk-v01.patch, HBASE-10411-v01.odt
>
>
> For kerberos 'request is a replay (34)' issue (HBASE-10379), adding it to the
> troubleshooting section in HBase book
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
