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] Updated: (HADOOP-5644) Namnode is stuck in safe mode
Date Thu, 09 Apr 2009 21:41:12 GMT

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

Suresh Srinivas updated HADOOP-5644:

    Attachment: 5644.branch-0.19.patch

# For branches 20 and trunk the block is not persisted in {{FSNamesystem.commitBlockSynchronization()}},
if append support is not enabled. Trunk patch can be applied to branch 20.
# For branches 18 and 19, since there is no flag to enable/disable support for append, block
is not persisted without any check for append support.

This needs to be revisited when append functionality is enabled (that is, even with append/sync,
if a block is persisted, the datanode must not delete the block from /tmp).

I have tested this fix manually on trunk.

> 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
>         Attachments: 5644.branch-0.18.patch, 5644.branch-0.19.patch, 5644.trunk.patch
> 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.

View raw message