[
https://issues.apache.org/jira/browse/ARTEMIS-4325?focusedWorklogId=866930&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-866930
]
ASF GitHub Bot logged work on ARTEMIS-4325:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Jun/23 10:19
Start Date: 22/Jun/23 10:19
Worklog Time Spent: 10m
Work Description: AntonRoskvist opened a new pull request, #4522:
URL: https://github.com/apache/activemq-artemis/pull/4522
Opening for feedback as this might not be the right solution. It does
however demonstrate the functionality I'm after.
If the feature makes sense on a high level, please let me know if the
implementation needs any changes or can be made better in some way.
Use case detailed in: https://issues.apache.org/jira/browse/ARTEMIS-4325
Issue Time Tracking
-------------------
Worklog Id: (was: 866930)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 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)
