[
https://issues.apache.org/jira/browse/HDFS-8881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912630#comment-16912630
]
Hadoop QA commented on HDFS-8881:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 14s{color}
| {color:red} HDFS-8881 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-8881 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12749409/HDFS-8881.00.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/27611/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Erasure Coding: internal blocks got missed and got over-replicated at the
> same time
> -----------------------------------------------------------------------------------
>
> Key: HDFS-8881
> URL: https://issues.apache.org/jira/browse/HDFS-8881
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: erasure-coding
> Reporter: Walter Su
> Assignee: Walter Su
> Priority: Major
> Attachments: HDFS-8881.00.patch
>
>
> We know the Repl checking depends on {{BlockManager#countNodes()}}, but
> countNodes() has limitation for striped blockGroup.
> *One* missing internal block will be catched by Repl checking, and handled by
> ReplicationMonitor.
> *One* over-replicated internal block will be catched by Repl checking, and
> handled by processOverReplicatedBlocks.
> *One* missing internal block and *two* over-replicated internal blocks *at
> the same time* will be catched by Repl checking, and handled by
> processOverReplicatedBlocks, later by ReplicationMonitor.
> *One* missing internal block and *One* over-replicated internal block *at the
> same time* will *NOT* be catched by Repl checking.
> "at the same time" means one missing internal block can't be recovered, and
> one internal block got over-replicated anyway. For example:
> scenario A:
> step 1. block #0 and #1 are reported missing.
> 2. a new #1 got recovered.
> 3. the old #1 come back, and the recovery work for #0 failed.
> scenario B:
> 1. An DN decommissioned/dead which has #1.
> 2. block #0 is reported missing.
> 3. The DN has #1 recommisioned, and the recovery work for #0 failed.
> In the end, the blockGroup has \[1, 1, 2, 3, 4, 5, 6, 7, 8\], assume 6+3
> schema. Client always needs to decode #0 if the blockGroup doesn't get
> handled.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
