[
https://issues.apache.org/jira/browse/HDFS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733768#action_12733768
]
Hairong Kuang commented on HDFS-265:
------------------------------------
>Page 4: "This algorithm chooses to do it right after 1.b and ..." Should "1.b"
>be "2.b"?
Writing data to disk is chosen to be done after 1.b. 1, 2, and 3 do not need to
be done in sequence.
> Page 3: when the replicator files in Datanodes are created? During Stage 1
> "Set up a pipeline"?
Replica files are created during pipeline set up time.
> Page 3: What will happen if a client setups a pipeline and then closes it?
> Will it result to some empty replicator files?
A pipeline does not get to set up unless an application already has written a
packet of data. So this scenario should not happen.
> Page 4: In "3. Simplify buffer management since ...", would it slow down the
> pipeline?
This is the same as what we have in the trunk. So it won't make the performance
worse.
> Revisit append
> --------------
>
> Key: HDFS-265
> URL: https://issues.apache.org/jira/browse/HDFS-265
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Attachments: appendDesign.pdf, appendDesign.pdf, AppendSpec.pdf,
> TestPlanAppend.html
>
>
> HADOOP-1700 and related issues have put a lot of efforts to provide the first
> implementation of append. However, append is such a complex feature. It turns
> out that there are issues that were initially seemed trivial but needs a
> careful design. This jira revisits append, aiming for a design and
> implementation supporting a semantics that are acceptable to its users.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
