[
https://issues.apache.org/jira/browse/HDFS-17054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18030893#comment-18030893
]
ASF GitHub Bot commented on HDFS-17054:
---------------------------------------
github-actions[bot] commented on PR #5760:
URL: https://github.com/apache/hadoop/pull/5760#issuecomment-3419090835
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> Erasure coding: optimize checkReplicaOnStorage method to avoid regarding all
> replicas on one datanode as corrupt repeatly.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-17054
> URL: https://issues.apache.org/jira/browse/HDFS-17054
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: farmmamba
> Priority: Critical
> Labels: pull-request-available
>
> Currently, when we execute countNodes method for a striped block, if a
> datanode has two ec blocks with different block id (because of some special
> cases and I will find and fix it laterly.). One block is LIVE, the other is
> CORRUPT. Current logic will compute two CORRUPT replicas because
> corruptReplicas contains the datanode. We should fix it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
