[
https://issues.apache.org/jira/browse/HDFS-16068?focusedWorklogId=611185&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-611185
]
ASF GitHub Bot logged work on HDFS-16068:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Jun/21 08:20
Start Date: 15/Jun/21 08:20
Worklog Time Spent: 10m
Work Description: tasanuma commented on pull request #3104:
URL: https://github.com/apache/hadoop/pull/3104#issuecomment-861292413
Thanks for your reviews and commits, @hemanthboyina and @tomscut. I will
cherry-pick to lower branches.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 611185)
Time Spent: 1h 20m (was: 1h 10m)
> 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
> Reporter: Takanobu Asanuma
> Assignee: Takanobu Asanuma
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
