activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-6372) KahaDB reader pool not releasing unused open files till deletion - too many open files
Date Mon, 25 Jul 2016 12:36:20 GMT

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

Gary Tully resolved AMQ-6372.
-----------------------------
    Resolution: Fixed

cleanup task now works as expected and during recovery only the current data file is retained
in the pool.

> KahaDB reader pool not releasing unused open files till deletion - too many open files
> --------------------------------------------------------------------------------------
>
>                 Key: AMQ-6372
>                 URL: https://issues.apache.org/jira/browse/AMQ-6372
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.13.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.14.0
>
>
> Leading to: 
> {code}java.io.FileNotFoundException: .../kahadb/db-2300.log (Too many open files){code}
> Kahadb has an accessor pool of random access files and a periodic cleanup. However the
cleanup does not work as expected.
> Only on journal gc does the pool get purged.
> This issue can arise with very large amounts of journal files that are paging and on
recovery when the entire journal needs to be replayed.
> In essence, currently there needs to be fd per journal data file.
> The workaround is to increase the nofiles (max open files) for the broker process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message