[
https://issues.apache.org/jira/browse/HDFS-17801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17987136#comment-17987136
]
ASF GitHub Bot commented on HDFS-17801:
---------------------------------------
hfutatzhanghb commented on PR #7774:
URL: https://github.com/apache/hadoop/pull/7774#issuecomment-3022462131
Hi @Hexiaoqiao @zhangshuyan0 @haiyang1987 . Could you please help review
this pr when you are free? Thanks a lot.
> EC: Reading support retryCurrentNode to avoid transient errors cause
> application level failures
> -----------------------------------------------------------------------------------------------
>
> 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
>
> *Description of PR*
> Under the 3-replication read implementation, when an IOException occurs,
> there is the retryCurrentNode mechanism.
> This is very useful to avoid application level failures due to transient
> errors (e.g. Datanode could have closed the connection because the client is
> idle for too long). Please refer to below codes :
> [https://github.com/apache/hadoop/blob/6eae1589aeea9bd9c6885e405bd9be5ef6199df7/hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/DFSInputStream.java#L824-L828]
> We should make EC read also support this mechanism.
> BTW, this issue is motivated by the failure of our cluster's applications
> failure when we change the data from 3-rep to EC policy.
> *How was this patch tested?*
> Add an unit test.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
