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 Tue, 14 Apr 2009 22:31:14 GMT

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

Suresh Srinivas commented on HADOOP-5644:

The failed tests are not related to this change. 

This functionality is tested manually as it is not easy to automate this test. To test this
patch run a command show below:
# Set {{dfs.safemode.threshld.pct}} to 1.000
# Run {{slowout | bin/hadoop fs -put - /test.out}}
where {{slowout}} is a command that outputs text slowly. While the output of the command is
being written to ~/test.out, kill the datanode to which client is writing to, followed by
the other datanodes to which the file is being pipelined to.
# Restart the cluster. The cluster gets stuck in safe mode without this patch. With this patch,
cluster starts up and automatically comes out of safe mode.

> Namnode is stuck in safe mode
> -----------------------------
>                 Key: HADOOP-5644
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5644
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.18.1, 0.18.2, 0.18.3, 0.19.0, 0.19.1
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.18.4, 0.19.2, 0.20.0, 0.21.0
>         Attachments: 5644.branch-0.18.patch, 5644.branch-0.18.patch, 5644.branch-0.18.patch,
5644.branch-0.19.patch, 5644.branch-0.19.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