[ 
https://issues.apache.org/jira/browse/ARTEMIS-4325?focusedWorklogId=874936&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-874936
 ]

ASF GitHub Bot logged work on ARTEMIS-4325:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Aug/23 13:58
            Start Date: 07/Aug/23 13:58
    Worklog Time Spent: 10m 
      Work Description: AntonRoskvist commented on PR #4522:
URL: 
https://github.com/apache/activemq-artemis/pull/4522#issuecomment-1667911830

   @jbertram @brusdev 
   
   Hello, back again from vacation.
   
   I made some changes as per our discussion and rebased against main. I'm 
still running the failback check in a separate thread since I didn't want to 
potentially stall/lock the TopologyHandler but now it's not starting until the 
node should be available (or available soon). Let me know what you think and 
see if there are any other changes that should be made here.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 874936)
    Time Spent: 1h  (was: 50m)

> Ability for core client 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: 1h
>  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)

Reply via email to