[
https://issues.apache.org/jira/browse/HDFS-11797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047116#comment-16047116
]
Yongjun Zhang commented on HDFS-11797:
--------------------------------------
Thanks you all for looking into this issue.
Hi [~kshukla], thanks for reporting and working the issue, I assume the release
you are running doesn't have HDFS-11445 fix.
My understanding of HDFS-11445 is, when we tried to remove a corrupt replica,
we only removed it from blockMap, and we "forgot" to remove it from the
corruptReplicaMap, thus caused the inconsistency.
Hi [~daryn], if my understanding is correct here, the fix you mentioned at
https://issues.apache.org/jira/browse/HDFS-11797?focusedCommentId=16042960&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042960
could be a follow-up jira. Do you agree?
Thanks.
> BlockManager#createLocatedBlocks() can throw ArrayIndexOutofBoundsException
> when corrupt replicas are inconsistent
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-11797
> URL: https://issues.apache.org/jira/browse/HDFS-11797
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Kuhu Shukla
> Assignee: Kuhu Shukla
> Priority: Critical
> Attachments: HDFS-11797.001.patch
>
>
> The calculation for {{numMachines}} can be too less (causing
> ArrayIndexOutOfBoundsException) or too many (causing NPE (HDFS-9958)) if data
> structures find inconsistent number of corrupt replicas. This was earlier
> found related to failed storages. This JIRA tracks a change that works for
> all possible cases of inconsistencies.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
