You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/04 08:12:00 UTC
[jira] [Commented] (HDFS-15552) Let DeadNode Detector also work for EC cases
[ https://issues.apache.org/jira/browse/HDFS-15552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802623#comment-17802623 ]
Shilun Fan commented on HDFS-15552:
-----------------------------------
Bulk update: moved all 3.4.0 non-blocker issues, please move back if it is a blocker. Retarget 3.5.0.
> 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
> Fix For: 3.4.0
>
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org