hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "qus-jiawei (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5341) DirectoryScanner hold the object lock dataset too long in scan,it make the datanode turn into deadnode and block all reciving thread
Date Tue, 22 Oct 2013 02:10:42 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801406#comment-13801406
] 

qus-jiawei commented on HDFS-5341:
----------------------------------

Asking for code review.

>  DirectoryScanner hold the object lock dataset too long in scan,it make the datanode
turn into deadnode and block all reciving thread
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-5341
>                 URL: https://issues.apache.org/jira/browse/HDFS-5341
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>            Reporter: qus-jiawei
>              Labels: deadlock
>             Fix For: 2.1.0-beta
>
>         Attachments: HDFS-5341.000.patch, HDFS-5341.001.patch, HDFS-5341.002.patch
>
>
> When DirectoryScanner doing the scan function, it holding the dataset to diff the block
info between memory and disk.But it do a lot of disk operation because it call the file's
getlength funciton.
> So,such disk operation should move to the async disk scan



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message