[
https://issues.apache.org/jira/browse/HADOOP-9850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732795#comment-13732795
]
Hadoop QA commented on HADOOP-9850:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12596705/HADOOP-9850.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{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:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2944//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2944//console
This message is automatically generated.
> RPC kerberos errors don't trigger relogin
> -----------------------------------------
>
> Key: HADOOP-9850
> URL: https://issues.apache.org/jira/browse/HADOOP-9850
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 3.0.0, 2.1.0-beta
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Blocker
> Attachments: HADOOP-9850.patch
>
>
> Hadoop auto-renews a ticket cache TGT. However, a TGT acquired via keytab is
> just allowed to expire. To compensate, any exception during a kerberos RPC
> connection triggers a relogin.
> Prior to HADOOP-9698, the RPC client "knew" the SASL client was attempting
> authMethod kerberos. Now the SASL client negotiates and returns the
> authMethod to the RPC Client. When an exception occurs, such as TGT expired,
> the Client doesn't know what the SASL client was attempting so no relogin is
> attempted. After 24 hours, keytab based services that act as clients (ex. RM
> for token renewal) go dead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
