[ 
https://issues.apache.org/jira/browse/HDFS-15908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shilun Fan updated HDFS-15908:
------------------------------
          Component/s: journal-node
     Target Version/s: 3.3.1, 3.4.0
    Affects Version/s: 3.3.1
                       3.4.0

> Possible Resource Leak in org.apache.hadoop.hdfs.qjournal.server.Journal
> ------------------------------------------------------------------------
>
>                 Key: HDFS-15908
>                 URL: https://issues.apache.org/jira/browse/HDFS-15908
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: journal-node
>    Affects Versions: 3.3.1, 3.4.0
>            Reporter: Narges Shadab
>            Assignee: Narges Shadab
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.3.1, 3.4.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> We noticed a possible resource leak 
> [here|https://github.com/apache/hadoop/blob/cd44e917d0b331a2d1e1fa63fdd498eac01ae323/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/server/Journal.java#L266].
>  The call to close on {{storage}} at line 267 can throw an exception. If it 
> occurs, then {{committedTxnId}} and {{curSegment}} are never closed.
> I'll submit a pull request to fix it.



--
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

Reply via email to