activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Andre Pearce (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-839) Support multiple backend data stores
Date Mon, 16 Apr 2018 16:46:00 GMT


Michael Andre Pearce commented on ARTEMIS-839:

[~clebertsuconic] did you get any progress on this. Indeed for ourselves, this is on our wishlist
e.g. there is genuine use case for this, though not that high priority for us as we just purchase
faster and bigger disks. But i noted this is on the roadmap docs for ActiveMQ 6 promotion
for Artemis. 


> Support multiple backend data stores
> ------------------------------------
>                 Key: ARTEMIS-839
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Matt Pavlovich
>            Priority: Major
> ActiveMQ 5.x supports multi-kahahdb where destinations matching the destination wildcard
naming convention are stored in separate data stores in order to overcome disk I/O performance
> Artemis should support this to achieve parity with ActiveMQ and other commercial brokers,
such as Tibco EMS that support multiple back-end data stores.
> The primary use case:
> 1. Increase overall disk I/O by having multiple mount points to allow busy destinations
to have separate disks
> Enhancement: It would be great if the full path could optionally be specified. Currently,
in ActiveMQ 5.x the path is automatically generated based on the destination name filter and
complicates the ability to separate destinations due to funky character names on all OS's
and filesystems.
> For example, support multiple journal entries:
> Examples:
>   *  < ... address-setting match="anycast://Ordering.#" path="file:/volumes/ordering">
>   * < .. address-setting match="anycast://Billing.#" path="file:/volumes/billing">
>   * < .. address-setting match="anycast://#" path="file:/volumes/default">

This message was sent by Atlassian JIRA

View raw message