hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-589) Change block write protocol to support pipeline recovery
Date Fri, 11 Sep 2009 23:21:57 GMT

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

Suresh Srinivas commented on HDFS-589:
--------------------------------------

Comments:
# DataTransferProtocol - add a comment to BlockConstructionStage.valueOf() with {{isRecovery()}}
to describe it handles both regular and recovery code. Also reordering any of the enums can
break this logic. A a comment to preserve the order.
# DataStreamer for append has {{if (freeInLastBlock > blockSize)}} check. It will never
be true right?


> Change block write protocol to support pipeline recovery
> --------------------------------------------------------
>
>                 Key: HDFS-589
>                 URL: https://issues.apache.org/jira/browse/HDFS-589
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: Append Branch
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: Append Branch
>
>         Attachments: opWriteProtocol.patch
>
>
> Current block write operation's header has the following fields:
> blockId blockGS pipelineSize isRecovery clientName hasSource source #datanodesInDownStreamPipeline
downstreamDatanodes
> I'd like to change the header to be
> blockId blockGS pipelineSize clientName  flags blockMinLen blockMaxLen newGS hasSource
source #datanodesInDownStreamPipeline downstreamDatanodes
> With this protocol change, pipeline recovery will be performed when a mew pipeline is
set up.

-- 
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