[
https://issues.apache.org/jira/browse/HDFS-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082366#comment-15082366
]
GAO Rui commented on HDFS-7661:
-------------------------------
See the {{4. Scenario 4: flush/sync was invoked more than one time in the same
strip.}} in [^HDFS-EC-file-flush-sync-design-version1.1.pdf]. Consider the
follow events sequences:
1. flush at {{Flush point 2.1}}, parity internal block: PIB1, PIB2 and PIB3
were calculated.
2. flush at {{Flush point 2.1.1}}, PIB1 and PIB2 were updated to PIB1` and PIB
2`, but PIB3 failed in updating.
3. PIB1`, the first and third data internal block were down.
4. Read file.
5. Recovery the missing data internal block using PIB2` and PIB3.
There we got a problem to recovery data correctly.
> 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)
