You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/08/19 02:28:45 UTC

[jira] [Commented] (HADOOP-12332) UserGroupInformation.reloginFromKeytab() timeout can leave UGI in unusable state

    [ https://issues.apache.org/jira/browse/HADOOP-12332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702226#comment-14702226 ] 

Steve Loughran commented on HADOOP-12332:
-----------------------------------------

doesn't sound like a deliberate design decision. Maybe there should be a catch() clause to reset the timestamp on a failure

> UserGroupInformation.reloginFromKeytab() timeout can leave UGI in unusable state
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-12332
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12332
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.6.0
>         Environment: affects all
>            Reporter: john lilley
>            Priority: Minor
>
> UserGroupInformation.reloginFromKeytab() sets the current timestamp before the try:
>     // register most recent relogin attempt
>     user.setLastLogin(now);
>     try {
> If a timeout error occurs during user.login() due to heavy system load, this leaves the user logged out and unusable, and because it has updated the timestamp, the caller cannot recover by calling reloginFromKeytab() immediately.
> It may be that timeouts should be considered fatal errors in this case, in which I would call it "as designed".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)