activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6815) KahaDB checkpoint needs to fail fast in the event of journal write failure
Date Thu, 11 Jan 2018 12:58:00 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322169#comment-16322169
] 

ASF subversion and git services commented on AMQ-6815:
------------------------------------------------------

Commit ec6fa190999160676cab900038b268b2d40a4d5c in activemq's branch refs/heads/master from
[~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=ec6fa19 ]

[AMQ-6815] rework to drop the batch reference from Location such that batches are free for
gc when index pages are agressively cached


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