hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-724) Pipeline close hangs if one of the datanode is not responsive.
Date Thu, 12 Nov 2009 14:57:39 GMT

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

dhruba borthakur commented on HDFS-724:
---------------------------------------

Agree that solution 1 will be simpler than solution 2. Another thing that might play a part
here is that, over time, we might want to add metadata to the heartbeat packet. (For example,
maybe the timestamp everytime a datanode forwards it; this will enable the client to eliminate
slow datanodes from the pipeline if needed.) 

> Pipeline close hangs if one of the datanode is not responsive.
> --------------------------------------------------------------
>
>                 Key: HDFS-724
>                 URL: https://issues.apache.org/jira/browse/HDFS-724
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node, hdfs client
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Hairong Kuang
>         Attachments: h724_20091021.patch
>
>
> In the new pipeline design, pipeline close is implemented by sending an additional empty
packet.  If one of the datanode does not response to this empty packet, the pipeline hangs.
 It seems that there is no timeout.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message