hadoop-hdfs-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/HDFS-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Todd Lipcon updated HDFS-2577:

    Attachment: hdfs-2577.txt

Attached patch changes back to the trunk behavior: only start the DT manager if security is
Also fixed another related bug I noticed while testing this fix -- with HDFS-2301 the lease
manager stop was always timing out, since it was looping on namesystem.isRunning() which continues
to be true even in standby mode. Added a flag to LeaseManager to decide whether the monitor
should run.

Tests seem to be passing now.
> 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


View raw message