hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Krogen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-11087) NamenodeFsck should check if the output writer is still writable.
Date Wed, 09 Nov 2016 22:52:58 GMT

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

Erik Krogen updated HDFS-11087:
    Attachment: HDFS-11087.branch-2.000.patch

Attaching v000 patch.

Since {{checkError}} internally calls {{flush}}, probably best not to do it _too_ frequently.
We already flush after processing every 100 files, so I piggybacked off of that, replacing
the call to {{flush}} with a call to {{checkError}} which will then throw an exception if
the stream has been closed / otherwise failed.  

> NamenodeFsck should check if the output writer is still writable.
> -----------------------------------------------------------------
>                 Key: HDFS-11087
>                 URL: https://issues.apache.org/jira/browse/HDFS-11087
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.6.5
>            Reporter: Konstantin Shvachko
>            Assignee: Erik Krogen
>         Attachments: HDFS-11087.branch-2.000.patch
> {{NamenodeFsck}} keeps running even after the client was interrupted. So if you start
{{fsck /}} on a large namespace and kill the client, the NameNode will keep traversing the
tree for hours although there is nobody to receive the result. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message