You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Teja sandeep (JIRA)" <ji...@apache.org> on 2016/04/27 13:28:12 UTC
[jira] [Updated] (AMQ-6265) Version 5.9.0 | KahaDB files not
getting cleaned up automatically.
[ https://issues.apache.org/jira/browse/AMQ-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Teja sandeep updated AMQ-6265:
------------------------------
Description:
Hi Team
We have recently faced a Blocker at our end where KahaDB files did not get cleaned up automatically and queued up for couple of days.
Unfortunately we did not notice this and the shared disk size became 100% full.
- This was a master/slave architecture where both are using the same shared drive. Hence ActiveMQ was unresponsive at this situation.
- We have moved the kahadb location to a temporary storage and got the disk cleaned up and pointed it back. Now the journal files are getting cleaned up automatically.
<persistenceAdapter>
<kahaDB directory="/data02/apphome/Broker" journalMaxFileLength="100mb" cleanupInterval="5000"/>
</persistenceAdapter>
was:
Hi Team
We have recently faced a Blocker at our end where KahaDB files did not get cleaned up automatically and queued up for couple of days.
Unfortunately we did not notice this and the shared disk size became 100% full.
- This was a master/slave architecture where both are using the same shared drive. Hence ActiveMQ was unresponsive at this situation.
- We have moved the kahadb location to a temporary storage and got the dick cleaned up and pointed it back. Now the journal files are getting cleaned up automatically.
<persistenceAdapter>
<kahaDB directory="/data02/apphome/Broker" journalMaxFileLength="100mb" cleanupInterval="5000"/>
</persistenceAdapter>
> Version 5.9.0 | KahaDB files not getting cleaned up automatically.
> ------------------------------------------------------------------
>
> Key: AMQ-6265
> URL: https://issues.apache.org/jira/browse/AMQ-6265
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-pool, KahaDB
> Reporter: Teja sandeep
>
> Hi Team
> We have recently faced a Blocker at our end where KahaDB files did not get cleaned up automatically and queued up for couple of days.
> Unfortunately we did not notice this and the shared disk size became 100% full.
> - This was a master/slave architecture where both are using the same shared drive. Hence ActiveMQ was unresponsive at this situation.
> - We have moved the kahadb location to a temporary storage and got the disk cleaned up and pointed it back. Now the journal files are getting cleaned up automatically.
> <persistenceAdapter>
> <kahaDB directory="/data02/apphome/Broker" journalMaxFileLength="100mb" cleanupInterval="5000"/>
> </persistenceAdapter>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)