hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhaoyunjiong (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5247) Namenode should close editlog and unlock storage when removing failed storage dir
Date Mon, 23 Sep 2013 03:04:03 GMT

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

zhaoyunjiong updated HDFS-5247:
-------------------------------

    Attachment: HDFS-5247-branch-1.2.patch

With this patch after restore storage:
[root@hd1-31851 ~]# lsof /volume1/
COMMAND   PID   USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
java    28831 hadoop   79uW  REG 252,32        0 393224 /volume1/nn/dfs/in_use.lock
java    28831 hadoop  113u   REG 252,32  1075255 393222 /volume1/nn/dfs/current/edits


                
> Namenode should close editlog and unlock storage when removing failed storage dir
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-5247
>                 URL: https://issues.apache.org/jira/browse/HDFS-5247
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 1.2.1
>            Reporter: zhaoyunjiong
>            Assignee: zhaoyunjiong
>             Fix For: 1.2.1
>
>         Attachments: HDFS-5247-branch-1.2.patch
>
>
> When one of dfs.name.dir failed, namenode didn't close editlog and unlock the storage:
> java    24764 hadoop   78uW  REG 252,32        0 393219 /volume1/nn/dfs/in_use.lock (deleted)
> java    24764 hadoop  107u   REG 252,32  1155072 393229 /volume1/nn/dfs/current/edits.new
(deleted)
> java    24764 hadoop  119u   REG 252,32        0 393238 /volume1/nn/dfs/current/fstime.tmp
> java    24764 hadoop  140u   REG 252,32  1761805 393239 /volume1/nn/dfs/current/edits
> If this dir is limit of space, then restore this storage may fail.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message