[
https://issues.apache.org/jira/browse/HDFS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733757#action_12733757
]
Hairong Kuang commented on HDFS-265:
------------------------------------
It looks that there are some confusions regarding the the pipeline diagram on
page 3. Each solid line does not represent one packet. Instead it represent the
starting of one packet and/or end of a packet. For example, t1 is the time that
packet 0 starts to be sent and t2 is the time that packet 0 is finished and
packet 1 gets started to be sent. Packet 2 is an hflushed packet. So packet 3
can not be sent before the ack for packet 2 is received.
This diagram assumes that application writes faster than packets get sent to
the network. So there is no waiting in between two packets. Hflush is called
before t3.
> 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.
