You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2008/05/22 00:57:55 UTC

[jira] Issue Comment Edited: (HADOOP-2159) Namenode stuck in safemode

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

hairong edited comment on HADOOP-2159 at 5/21/08 3:57 PM:
----------------------------------------------------------------

Please note that the cluster did have stale blocks. As shown in the fsck result, the ratio of the minimally replicated blocks to the total number of valid blocks is greater than 100%,

      was (Author: hairong):
    Please note that the cluster did have stale blocks. The ratio of the minimally replicated blocks to the total number of valid blocks is greater than 100%,
  
> 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.