hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5644) Namnode is stuck in safe mode
Date Wed, 08 Apr 2009 23:56:12 GMT

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

Suresh Srinivas commented on HADOOP-5644:
-----------------------------------------

Proposed solution:
When a client encounters a problem, it tries to recover the block. During block recovery,
{{FSNamesystem.commitBlockSynchronization()}} the information related to the block is persisted.
Namenode during restart, loads the information related to the failed block. The solution is
not to persist the block synchronization during block recovery.

> Namnode is stuck in safe mode
> -----------------------------
>
>                 Key: HADOOP-5644
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5644
>             Project: Hadoop Core
>          Issue Type: Bug
>    Affects Versions: 0.18.1, 0.18.2, 0.18.3, 0.19.0, 0.19.1
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>
> Restarting datanodes while a client is writing to it can cause namenode to get stuck
in safe mode.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message