activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Pavlovich (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARTEMIS-839) Support multiple backend data stores
Date Thu, 13 Apr 2017 14:47:42 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Matt Pavlovich updated ARTEMIS-839:
-----------------------------------
    Description: 
ActiveMQ 5.x supports multi-kahahdb where destinations matching a certain 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">



   
    

  was:
ActiveMQ 5.x supports multi-kahahdb where destinations matching a certain 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="Ordering.#" path="file:/volumes/ordering">
  * < .. address-setting match="Billing.#" path="file:/volumes/billing">
  * < .. address-setting match="#" path="file:/volumes/default">



   
    


> Support multiple backend data stores
> ------------------------------------
>
>                 Key: ARTEMIS-839
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-839
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Matt Pavlovich
>
> ActiveMQ 5.x supports multi-kahahdb where destinations matching a certain 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">
>    
>     



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message