activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-6815) KahaDB checkpoint needs to fail fast in the event of journal write failure
Date Thu, 11 Jan 2018 13:08:00 GMT

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

Christopher L. Shannon updated AMQ-6815:
----------------------------------------
    Fix Version/s: 5.15.3

> KahaDB checkpoint needs to fail fast in the event of journal write failure
> --------------------------------------------------------------------------
>
>                 Key: AMQ-6815
>                 URL: https://issues.apache.org/jira/browse/AMQ-6815
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.15.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.16.0, 5.15.3
>
>
> KahaDB checkpoint does some async updated to the journal and syncs to the index. However
the async journal updates can error out and not get reported leading to the index metadata
being stale. This can lead to reading an invalid location on restart which may result in full
recovery of the index.
> Any exception from the async store needs to cause the checkpoint to fail.
> In addition, on reading a corrupt location, we can do a sanity check to avoid a potential
OOM by validating the size before allocation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message