You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/01/07 19:46:00 UTC
[jira] [Updated] (ARTEMIS-4325) Ability for core client to failback after failover
[ https://issues.apache.org/jira/browse/ARTEMIS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated ARTEMIS-4325:
------------------------------------
Labels: pull-request-available (was: )
> Ability for core client to failback after failover
> --------------------------------------------------
>
> Key: ARTEMIS-4325
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4325
> Project: Artemis
> Issue Type: New Feature
> Reporter: Anton Roskvist
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> This would be similar to the "priorityBackup" functionality in ActiveMQ "Classic."
> The primary use case for this is to more easily maintain a good distribution of consumers and producers across a broker cluster over time.
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org