[
https://issues.apache.org/jira/browse/HDFS-15552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044002#comment-18044002
]
ASF GitHub Bot commented on HDFS-15552:
---------------------------------------
github-actions[bot] commented on PR #2287:
URL: https://github.com/apache/hadoop/pull/2287#issuecomment-3634837332
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.
> Let DeadNode Detector also work for EC cases
> --------------------------------------------
>
> Key: HDFS-15552
> URL: https://issues.apache.org/jira/browse/HDFS-15552
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: dfsclient, ec
> Affects Versions: 3.3.0
> Reporter: dark_num
> Assignee: imbajin
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, the EC stream (`DFSStripedInputStream`) is not handled properly
> while exception occurs.
> For example, while reading EC-blocks, if the client timed out when connecting
> to the DataNode, it will throws `SocketTimeoutException` , then add current
> DN to localDeadNode.
> However, the local dead nodes will not be removed until the stream is closed,
> which will cause *missing block IOException* to be thrown in the use scenario
> of Hbase.
> So we need to use detector to deal with dead nodes under EC to avoid reading
> failures.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
