hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2577) HA: NN fails to start since it tries to start secret manager in safemode
Date Thu, 24 Nov 2011 00:52:40 GMT

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

Todd Lipcon commented on HDFS-2577:
-----------------------------------

The LM changes don't need to be done on trunk, because on the non-HA branch, FSNamesystem.isRunning
is an accurate gauge of whether the LM should run. On HDFS it's not the case anymore since
in standby mode, the LM doesn't run, even though the FSN is "running". I'll check this into
the HA branch, thanks!
                
> HA: NN fails to start since it tries to start secret manager in safemode
> ------------------------------------------------------------------------
>
>                 Key: HDFS-2577
>                 URL: https://issues.apache.org/jira/browse/HDFS-2577
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hdfs-2577.txt
>
>
> After HDFS-2301, the NN fails to start with the following:
> Caused by: org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot log master
key update in safe mode. Name node is in safe mode.
> The reported blocks 0 needs additional 5 blocks to reach the threshold 1.0000 of total
blocks 4. Safe mode will be turned off automatically.
>         at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.logUpdateMasterKey(FSNamesystem.java:4259)
>         at org.apache.hadoop.hdfs.security.token.delegation.DelegationTokenSecretManager.logUpdateMasterKey(DelegationTokenSecretManager.java:285)
>         at org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager.updateCurrentKey(AbstractDelegationTokenSecretManager.java:143)
>         at org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager.startThreads(AbstractDelegationTokenSecretManager.java:98)
>         at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startSecretManager(FSNamesystem.java:386)
>         at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startActiveServices(FSNamesystem.java:440)
>         at org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.startActiveServices(NameNode.java:937)
>         at org.apache.hadoop.hdfs.server.namenode.ha.ActiveState.enterState(ActiveState.java:57)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message