[
https://issues.apache.org/jira/browse/HDFS-7672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531700#comment-14531700
]
Tsz Wo Nicholas Sze commented on HDFS-7672:
-------------------------------------------
> shouldLocateFollowingBlock doesn't look good but since it's inherited I'll
> file another JIRA to address it.
I found that we actually could check if block==null but not need another
variable. I will fix it in HDFS-8323.
> Erasure Coding: consolidate streamer coordination logic and handle failure
> when writing striped blocks
> ------------------------------------------------------------------------------------------------------
>
> Key: HDFS-7672
> URL: https://issues.apache.org/jira/browse/HDFS-7672
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Fix For: HDFS-7285
>
> Attachments: h7672_20150504.patch, h7672_20150504b.patch,
> h7672_20150504c.patch, h7672_20150505.patch, h7672_20150505b.patch
>
>
> In *stripping* case, for (6, 3)-Reed-Solomon, a client writes to 6 data
> blocks and 3 parity blocks concurrently. We need to handle datanode or
> network failures when writing a EC BlockGroup.
> We also refactor the existing code in DFSStripedOutputStream and
> StripedDataStreamer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
