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 "Aaron T. Myers (JIRA)" <ji...@apache.org> on 2013/06/11 01:37:20 UTC

[jira] [Commented] (HADOOP-9589) Extra master key is created when AbstractDelegationTokenSecretManager is started

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

Aaron T. Myers commented on HADOOP-9589:
----------------------------------------

Hey Jian, can you summarize here what effect this has, if any?

Thanks a lot.
                
> Extra master key is created when AbstractDelegationTokenSecretManager is started
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-9589
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9589
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Jian He
>            Assignee: Jian He
>
> When AbstractDelegationTokenSecretManager starts , AbstractDelegationTokenSecretManager.startThreads().updateCurrentKey() creates the first master key. Immediately after that, ExpiredTokenRemover thread is started, and it will creates the second master by calling rollMasterKey on its first loop.

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