[
https://issues.apache.org/jira/browse/HDFS-15552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807693#comment-17807693
]
Imba Jin commented on HDFS-15552:
---------------------------------
[~slfan1989] Thanks for the reminder & update, due to long time no update with
it maybe I miss the full context & won't update it in the near future
I checked the modification in PR, seems it lacks the proper UT before
So someone could consider cherry-pick the commit & add the basic test for it &
then close/mark this as complete?
> 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]
