[
https://issues.apache.org/jira/browse/HDFS-17801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038717#comment-18038717
]
ASF GitHub Bot commented on HDFS-17801:
---------------------------------------
github-actions[bot] commented on PR #7774:
URL: https://github.com/apache/hadoop/pull/7774#issuecomment-3539528580
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.
> EC supports createBlockReader retry when IOException occurs
> -----------------------------------------------------------
>
> Key: HDFS-17801
> URL: https://issues.apache.org/jira/browse/HDFS-17801
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: farmmamba
> Assignee: farmmamba
> Priority: Major
> Labels: pull-request-available
>
> Currently , there is no retry policy If we meet IOExcetion when creating
> block reader to read EC file. Suppose below case (using RS-6-3-1024k):
> The first 4 to 6 data blocks' datanodes are very busy at the same time,
> createBlockReader will timeout. This will cause read failure, we should make
> EC support retry mechanism to mitigate read failure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
