hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prakash (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5341) DirectoryScanner hold the object lock dataset too long in scan,that make the datanode turn into deadnode and block all reciving thread
Date Wed, 23 Oct 2013 20:15:50 GMT

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

Ravi Prakash commented on HDFS-5341:
------------------------------------

Thanks Jiawei! This is a good change and this patch looks good to me. +1. Can a committer
please review and commit this patch? The test TestBlocksWithNotEnoughRacks failure is not
related to this patch. It is being tracked at HDFS-3267.

>  DirectoryScanner hold the object lock dataset too long in scan,that 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
>            Assignee: qus-jiawei
>              Labels: deadlock
>             Fix For: 3.0.0
>
>         Attachments: HDFS-5341.000.patch, HDFS-5341.001.patch, HDFS-5341.002.patch, HDFS-5341.003.patch,
HDFS-5341.004.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.
> Once the dataset is locked,heartbeat thread and all DataXceiver thread would be blocked.
> 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