[
https://issues.apache.org/jira/browse/HDFS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932270#action_12932270
]
stack commented on HDFS-724:
----------------------------
I tried it by running a few of the hbase tests that were failing before
hbAckReply.patch. They pass now (with hdfs-895 in place on 0.20-append). Let
me run the full suite. I'll report back.
One issue that came up over in hbase-3234 was the fact that hdfs-724 does this:
{code}
- public static final int DATA_TRANSFER_VERSION = 14;
+ public static final int DATA_TRANSFER_VERSION = 15;
{code}
Could we not do the above on commit to 0.20-append? No biggie. Just asking.
Would be nice not making comm incompatible. Good stuff Hairong.
> 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
> Affects Versions: 0.21.0
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Hairong Kuang
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: h724_20091021.patch, hbAckReply.patch,
> pipelineHeartbeat.patch, pipelineHeartbeat1.patch, pipelineHeartbeat2.patch,
> stuckWriteAppend20.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.
