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-5603) Consider preallocation of journal files in batch increments
Date Thu, 05 May 2016 12:08:12 GMT

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

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

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

https://issues.apache.org/jira/browse/AMQ-5603 - reverting default preallocatonScope to entire_journal
b/c async only really works for ssd


> Consider preallocation of journal files in batch increments
> -----------------------------------------------------------
>
>                 Key: AMQ-5603
>                 URL: https://issues.apache.org/jira/browse/AMQ-5603
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Message Store
>            Reporter: Christian Posta
>            Assignee: Gary Tully
>            Priority: Minor
>              Labels: kahaDB, perfomance
>             Fix For: 5.14.0
>
>
> Right now (as of ActiveMQ 5.12 release) we preallocate journal files, but the only scope
is for entire journal file. The [potential] issue with that is if user configures large journal
file sizes, we can end up stalling writes during log rotation because of the allocation process.
There are two ways to do the allocation, configurable to do it in userspace, or defer to kernel
space, but nevertheless it would be good to avoid this issue altogether by preallocating in
small batch sizes regardless of the journal max file size.



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

Mime
View raw message