[
https://issues.apache.org/jira/browse/HDFS-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085278#comment-15085278
]
GAO Rui commented on HDFS-7661:
-------------------------------
Thank you [~walter.k.su]. I understand your concern now. You are right, in
{{Scenario 4: flush/sync was invoked more than one time in the same strip}},
the described dealing steps risk the safety of data written before 1st flush
when over written parity internal blocks.
I will consider this problem and try to figure out a better design. Thank you
very much for pointing out this problem!
> Erasure coding: support hflush and hsync
> ----------------------------------------
>
> Key: HDFS-7661
> URL: https://issues.apache.org/jira/browse/HDFS-7661
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Tsz Wo Nicholas Sze
> Assignee: GAO Rui
> Attachments: EC-file-flush-and-sync-steps-plan-2015-12-01.png,
> HDFS-7661-unitTest-wip-trunk.patch,
> HDFS-EC-file-flush-sync-design-version1.1.pdf
>
>
> We also need to support hflush/hsync and visible length.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
