[ 
https://issues.apache.org/jira/browse/HDFS-15709?focusedWorklogId=521461&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-521461
 ]

ASF GitHub Bot logged work on HDFS-15709:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Dec/20 23:49
            Start Date: 07/Dec/20 23:49
    Worklog Time Spent: 10m 
      Work Description: jojochuang merged pull request #2518:
URL: https://github.com/apache/hadoop/pull/2518


   


----------------------------------------------------------------
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: 521461)
    Time Spent: 0.5h  (was: 20m)

> EC: Socket file descriptor leak in StripedBlockChecksumReconstructor
> --------------------------------------------------------------------
>
>                 Key: HDFS-15709
>                 URL: https://issues.apache.org/jira/browse/HDFS-15709
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode, ec, erasure-coding
>            Reporter: Yushi Hayasaka
>            Assignee: Yushi Hayasaka
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We found a socket file descriptor leak when we tried to get the checksum of 
> EC file with reconstruction happened during the operation.
> The cause of the leak seems that the StripedBlockChecksumReconstructor does 
> not close StripedReader. Making the reader closed, the CLOSE_WAIT connections 
> are gone.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to