You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2009/09/27 23:00:19 UTC
[jira] Updated: (HDFS-642) Support pipeline close and close
recovery
[ https://issues.apache.org/jira/browse/HDFS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hairong Kuang updated HDFS-642:
-------------------------------
Attachment: closePipeline.patch
A patch for review. It additionally has another change:
A block receiver moves a packet to the ack queue before the received data is flushed to the disk. This means that a packet may be acked bfore its data is on disk.
> Support pipeline close and close recovery
> -----------------------------------------
>
> Key: HDFS-642
> URL: https://issues.apache.org/jira/browse/HDFS-642
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: Append Branch
>
> Attachments: closePipeline.patch
>
>
> This jira intends to implement the third stage of block construction: close. The main ideas are:
> 1. A client notifies the datanodes in the pipeline to finalize a replica and then shuts down the pipeline by sending a special end-of-block message.
> 2. The end-of-block message does not get sent until the client finishes sending all packets belong to the block and have received all their acks.
> 3. If close fails, the client recovers the failures by setting up a new pipeline with the remaining datanodes and a newer generation stamp.
> 4. I plan to use an empty packet as the end-of-block message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.