[
https://issues.apache.org/jira/browse/ARTEMIS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Roskvist updated ARTEMIS-4325:
------------------------------------
Description:
This would be similar to the "priorityBackup" functionality in the ActiveMQ 5
broker.
The primary use case for this is to more easily maintain a good distribution of
consumers and producers across a broker cluster.
The intended behavior for my own purposes would be something like:
- Ensure an even distribution across the broker cluster when first connecting
a high throughput client.
- When a broker becomes unavailable (network outage, patch, crash, whatever),
move affected client workers to another broker in the cluster to maintain
throughput.
- When the original broker comes back, move the recently failed over resources
to the original broker again.
was:
This would be similar to the "priorityBackup" functionality in the ActiveMQ 5
broker.
The primary use case for this is to more easily maintain a good distribution of
consumers and producers across a broker cluster.
The intended behavior for my own purposes would be something like:
- Ensure an even distribution across the broker cluster when first connecting a
high throughput client.
- When a broker becomes unavailable (network outage, patch, crash, whatever),
move affected client workers to another broker in the cluster to maintain
throughput.
- When the original broker comes back, move the recently failed over resources
to the original broker again.
> Ability to failback after failover
> ----------------------------------
>
> Key: ARTEMIS-4325
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4325
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Anton Roskvist
> Priority: Major
>
> This would be similar to the "priorityBackup" functionality in the ActiveMQ 5
> broker.
> The primary use case for this is to more easily maintain a good distribution
> of consumers and producers across a broker cluster.
>
> The intended behavior for my own purposes would be something like:
> - Ensure an even distribution across the broker cluster when first
> connecting a high throughput client.
> - When a broker becomes unavailable (network outage, patch, crash,
> whatever), move affected client workers to another broker in the cluster to
> maintain throughput.
> - When the original broker comes back, move the recently failed over
> resources to the original broker again.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
