[
https://issues.apache.org/jira/browse/HDFS-14754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924081#comment-16924081
]
Surendra Singh Lilhore commented on HDFS-14754:
-----------------------------------------------
Thanks [~hemanthboyina] for patch.
Some comment for test.
# This test code is not able to reproduce this issue currently, the logic of
creating redundant block is wrong, it should be something like this.
{code:java}
// one missing block
for (; i < groupSize - 1; i++) {
blk.setBlockId(groupId + i);
cluster.injectBlocks(i, Arrays.asList(blk), bpid);
}
cluster.triggerBlockReports();
// one redundant block
blk.setBlockId(groupId + 2);
cluster.injectBlocks(i, Arrays.asList(blk), bpid); {code}
# DFS_NAMENODE_REPLICATION_MAX_STREAMS_KEY configured with 0, this will not
allow NN to reconstruct the block. This configuration is not required.
#
{code:java}
+ final LocatedBlock[] blocks =
+ StripedBlockUtil.parseStripedBlockGroup(bg, cellSize, 5, 1);{code}
Here pass correct parity and data block count.
> Erasure Coding : The number of Under-Replicated Blocks never reduced
> ---------------------------------------------------------------------
>
> Key: HDFS-14754
> URL: https://issues.apache.org/jira/browse/HDFS-14754
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: hemanthboyina
> Assignee: hemanthboyina
> Priority: Critical
> Attachments: HDFS-14754.001.patch, HDFS-14754.002.patch,
> HDFS-14754.003.patch
>
>
> Using EC RS-3-2, 6 DN
> We came accross a scenario where in the EC 5 blocks , same block is
> replicated thrice and two blocks got missing
> Replicated block was not deleting and missing block is not able to ReConstruct
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
