[
https://issues.apache.org/jira/browse/HDFS-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597142#comment-14597142
]
Zhe Zhang commented on HDFS-8619:
---------------------------------
bq. I guess we still need this jira for adding the striped block logic and the
tests.
Sure. I see at least the tests are specific to striped blocks.
bq. Besides, we now have merged quite a few changes to trunk, any plan for
merging trunk changes to the HDFS-7285 feature branch?
Thanks for bringing up the question Jing. These days I'm mostly focused on this
front. Since the merged changes are quite big, I'm rebasing the entire
consolidated HDFS-7285 patch instead of individual patches. Late last week I
finished a first round of rebasing which is quite rough. I posted a [comment
https://issues.apache.org/jira/browse/HDFS-7285?focusedCommentId=14593827&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14593827]
but I guess it is hidden in between Hudson messages (could you help delete
them?). I'm working on a second round of rebase to include all changes.
Hopefully also to split it to functional pieces like "Support EC zones",
"Allocate and persist striped blocks in NameNode", ""Add striped block support
in INodeFile.". I'll post a new rebased patch soon.
> Erasure Coding: revisit replica counting for striped blocks
> -----------------------------------------------------------
>
> Key: HDFS-8619
> URL: https://issues.apache.org/jira/browse/HDFS-8619
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-8619.000.patch
>
>
> Currently we use the same {{BlockManager#countNodes}} method for striped
> blocks, which simply treat each internal block as a replica. However, for a
> striped block, we may have more complicated scenario, e.g., we have multiple
> replicas of the first internal block while we miss some other internal
> blocks. Using the current {{countNodes}} methods can lead to wrong decision
> in these scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
