hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9049) DelegationTokenRenewer needs to be Singleton and FileSystems should register/deregister to/from.
Date Mon, 19 Nov 2012 15:27:01 GMT

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

Daryn Sharp commented on HADOOP-9049:
-------------------------------------

+1 But I'd suggest canceling the token in {{removeRenewAction}}.  Hftp & webhdfs only
register tokens for renewal that are implicitly created for internal use.  Since they aren't
cancelled, it causes a bunch of defunct tokens to clog the NN until they expire.  If you want
to fix it on another jira, I'm fine with that.
                
> DelegationTokenRenewer needs to be Singleton and FileSystems should register/deregister
to/from.
> ------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9049
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9049
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.0.2-alpha
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: hadoop-9049.patch, hadoop-9049.patch
>
>
> Currently, DelegationTokenRenewer is not singleton.
> Each filesystem using it spawns its own DelegationTokenRenewer. Also, they don't stop
the Renewer leading to other problems.
> A single DelegationTokenRenewer should be sufficient for all FileSystems.

--
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

Mime
View raw message