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-6771) Improve performance of KahaDB recovery check checkForCorruptJournalFiles=true
Date Tue, 18 Jul 2017 11:29:00 GMT

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

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

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

[AMQ-6771] fix off by one on input stream read long check, with test


> Improve performance of KahaDB recovery check checkForCorruptJournalFiles=true
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-6771
>                 URL: https://issues.apache.org/jira/browse/AMQ-6771
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: KahaDB
>    Affects Versions: 5.15.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.16.0
>
>
> The KahaDB checkForCorruptJournalFiles option validates the checksum of every journal
batch record on startup. If a single producer writes many small messages, the batch sizes
in the journal will be small. The current check implementation reads each batch at a time
with a fseek/read sequence that can be very slow over shared disks.
> The check can be a quick buffered sequential read using the maxBatchSize which should
already be tuned to match the disk transfer rate.



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

Mime
View raw message