You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2025/01/06 21:51:00 UTC
[jira] [Resolved] (HDFS-17080) Fix ec connection leak (GitHub PR#5807)
[ https://issues.apache.org/jira/browse/HDFS-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei-Chiu Chuang resolved HDFS-17080.
------------------------------------
Fix Version/s: 3.5.0
Resolution: Fixed
> Fix ec connection leak (GitHub PR#5807)
> ---------------------------------------
>
> Key: HDFS-17080
> URL: https://issues.apache.org/jira/browse/HDFS-17080
> Project: Hadoop HDFS
> Issue Type: Task
> Reporter: Wei-Chiu Chuang
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0
>
>
> Creating this jira to track GitHub PR #5807.
> {quote}Description of PR
> This PR fixes EC connection leak if got exception when constructing reader.
> How was this patch tested?
> Cluster: Presto
> Data: EC
> Query: select col from table(EC data) limit 10
> Presto is a long time running process to deal with query.
> In this case, when it gets 10 records, it will interrupt other threads.
> Other threads may be in constructing reader or getting next record.
> If getting next record is interrupted, it will be caught and Presto will close it.
> But if constructing reader is interrupted, Presto cannot close it because reader in Presto has not been created.
> So we can observe whether EC connection is closed when doing EC limit query.
> Use netstat command.{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org