[ARTEMIS-839] Support multiple backend data stores

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Broker
• Assignee: Unassigned
• Reporter: Matt Pavlovich
• Created: 04/Nov/16 21:16
• Updated: 16/Apr/18 16:45

Description

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 issues

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