[
https://issues.apache.org/jira/browse/HDFS-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082145#comment-15082145
]
GAO Rui commented on HDFS-7661:
-------------------------------
Hi [~zhz], it's a good idea to store the length info in {{.meta}} file.
The additional locks is for the situation in which failures happened. For
example, we have a block group consisted by 6 data internal blocks and 3 parity
internal blocks. When updating the length of this block group, we might failed
to update 1 of the 3 parity internal blocks. But, the *older* parity internal
block comes back later, then we have different version parity blocks. It could
cause problems when further possible internal block recovery happens.
> 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)
