[
https://issues.apache.org/jira/browse/HDFS-16068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated HDFS-16068:
------------------------------
Component/s: webhdfs
Hadoop Flags: Reviewed
Target Version/s: 3.3.2, 3.2.3, 2.10.2, 3.4.0
Affects Version/s: 3.3.2
3.2.3
2.10.2
3.4.0
> WebHdfsFileSystem has a possible connection leak in connection with HttpFS
> --------------------------------------------------------------------------
>
> Key: HDFS-16068
> URL: https://issues.apache.org/jira/browse/HDFS-16068
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 3.4.0, 2.10.2, 3.2.3, 3.3.2
> Reporter: Takanobu Asanuma
> Assignee: Takanobu Asanuma
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 2.10.2, 3.2.3, 3.3.2
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> When we use WebHdfsFileSystem for HttpFS, some connections remain for a while
> after the filesystems are closed until GC runs. After investigating it for a
> while, I found that there is a potential connection leak in WebHdfsFileSystem.
> {code:java}
> // Close both the InputStream and the connection.
> @VisibleForTesting
> void closeInputStream(RunnerState rs) throws IOException {
> if (in != null) {
> IOUtils.close(cachedConnection);
> in = null;
> }
> cachedConnection = null;
> runnerState = rs;
> }
> {code}
> In the above code, if the variable of {{in}} is null and {{cachedConnection}}
> is not null, {{cachedConnection}} doesn't close and the connection remains. I
> think this is the cause of our problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
