[ https://issues.apache.org/jira/browse/ARTEMIS-4251?focusedWorklogId=858714&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858714 ]
ASF GitHub Bot logged work on ARTEMIS-4251: ------------------------------------------- Author: ASF GitHub Bot Created on: 24/Apr/23 13:18 Start Date: 24/Apr/23 13:18 Worklog Time Spent: 10m Work Description: AntonRoskvist commented on PR #4447: URL: https://github.com/apache/activemq-artemis/pull/4447#issuecomment-1520145971 Really nice addition. Haven't really looked into how it can be implemented, but there is a feature in "ActiveMQ Classic" that I think would be a great addition on top of this change. It's called "priorityBackup" ( https://activemq.apache.org/failover-transport-reference.html#priority-backup ) It has the client perform this type of failover to carry on its work, but then afterwards tries to continuously connect back to the original broker, releasing the new connection if/when it succeeds. This is good for handling client distribution across a broker cluster that sort of "persists" through maintenance, crashes, network outages etc on the broker side. Either way, this is a really nice addition as is! Issue Time Tracking ------------------- Worklog Id: (was: 858714) Time Spent: 20m (was: 10m) > Support CORE client failover to other live servers > -------------------------------------------------- > > Key: ARTEMIS-4251 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4251 > Project: ActiveMQ Artemis > Issue Type: Improvement > Reporter: Domenico Francesco Bruscino > Assignee: Domenico Francesco Bruscino > Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The CORE clients support failover only reconnecting to the current > live/backup pair. Improve the CORE client failover connecting to other live > servers when all reconnect attempts fails, i.e. in a cluster composed of 2 > live servers, when the server to which the CORE client is connected goes down > the CORE client should reconnect its sessions to the other liver broker. -- This message was sent by Atlassian Jira (v8.20.10#820010)