hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3541) Deadlock between recovery, xceiver and packet responder
Date Thu, 21 Jun 2012 22:25:43 GMT

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

Kihwal Lee commented on HDFS-3541:
----------------------------------

bq. But as of now there is no way to stop the PacketResponder

When (DataXciever) writer gets interrupted, it can fire an interrupt to (PacketResponder)
responder. If we put a Thread.interrupted() check in finalizeBlock() and let it bail out or
throw an InterruptedException, we can stop responder. Of course, PacketResponder will also
need some changes to propely handle the exception. What do you think?
                
> Deadlock between recovery, xceiver and packet responder
> -------------------------------------------------------
>
>                 Key: HDFS-3541
>                 URL: https://issues.apache.org/jira/browse/HDFS-3541
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>    Affects Versions: 0.23.3, 2.0.1-alpha
>            Reporter: suja s
>            Assignee: Vinay
>         Attachments: DN_dump.rar
>
>
> Block Recovery initiated while write in progress at Datanode side. Found a lock between
recovery, xceiver and packet responder.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message