[jira] [Updated] (AMQ-6134) ActiveMQ corrupted state when local disk fills up and Queues fill up

["Paul Smith (JIRA)" <ji...@apache.org>]

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

Paul Smith updated AMQ-6134:
----------------------------
    Attachment: activemq.log

Attached activemq.log.  The service had been up for months with no issues, so this is a daily rotated log, hardly anything in there until the world comes crashing down when the disk filled up.

> ActiveMQ corrupted state when local disk fills up and Queues fill up
> --------------------------------------------------------------------
>
>                 Key: AMQ-6134
>                 URL: https://issues.apache.org/jira/browse/AMQ-6134
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.11.1
>            Reporter: Paul Smith
>            Priority: Critical
>         Attachments: activemq.log
>
>
> There are already issues reporting this in AMQ-3098 and AMX-5786 but they have been closed as Incomplete, I've left a comment on 5786 but I fear that it may get lost.
> Fundamentally KahaDB & ActiveMQ do not survive if Queues start filling up and buffering to KahaDB disk when the disk then becomes full because of an external issue (in our case rsyslog).
> Because KahaDB does not pre-allocate space, it seems vunerable to this case.
> I will attach broker logs and Kahadb store during the corrupted state.



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