[
https://issues.apache.org/jira/browse/HADOOP-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598841#action_12598841
]
Koji Noguchi commented on HADOOP-2159:
--------------------------------------
We also had one cluster that didn't come out of safemode.
fsck showed,
{noformat}
Status: HEALTHY
Total dirs: 270001
Total files: 1036456
Total blocks: 1982902 (avg. block size 92619603 B)
Minimally replicated blocks: 1982902 (100.00001 %)
Over-replicated blocks: 0 (0.0 %)
Under-replicated blocks: 0 (0.0 %)
Mis-replicated blocks: 0 (0.0 %)
Default replication factor: 3
Average block replication: 3.0000212
Missing replicas: 0 (0.0 %)
The filesystem under path '/' is HEALTHY
{noformat}
I attached btrace to obtain the state of Namenode.namesystem.safeMode,
{noformat}
-bash-3.1$ pgrep -f NameNode
30490
-bash-3.1$ btrace -cp hadoop-core.jar 30490 DFSSafeModeTrace.java
entered org.apache.hadoop.dfs.FSNamesystem.isInSafeMode
[EMAIL PROTECTED]
{threshold=1.0, extension=30000, safeReplication=1, reached=0,
blockTotal=1982902, blockSafe=1982812,
[EMAIL PROTECTED], }
{noformat}
This shows that blockSafe < blockTotal, which supports Hairong's comment above.
(dfs.safemode.threshold.pct is set to 1.0f)
> Namenode stuck in safemode
> --------------------------
>
> Key: HADOOP-2159
> URL: https://issues.apache.org/jira/browse/HADOOP-2159
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: Christian Kunz
>
> Occasionally (not easy to reproduce) the namenode does turn off safemode
> automatically, although fsck does not report any missing or under-replicated
> blocks (safemode threshold set to 1.0).
> At this moment I do not have any additional information which could help
> analyze the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
