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:54:12 GMT

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

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

A client is writing data to datanode D1, with pipeline to datanodes D2 and D3. Restarting
D1, followed by D2 and D3 results in:
1. File that client was writing gets stuck in the state under construction. Restarting the
cluster or lease recovery timeout does not finalize the file.
2. Block that client was writing to is deleted by the datanodes during restart. If the namenode
is configured with safemode threshold of 1.0, on restart it does not come out of safemode,
since the deleted block is never reported by any datanode.

> 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