AntonRoskvist commented on PR #4522:
URL:
https://github.com/apache/activemq-artemis/pull/4522#issuecomment-1610117640
@brusdev
@jbertram
Thanks for your feedback, much appreciated!
In the case of failback between HA live/backup-pairs, that should be covered
already. Since failback would only follow a failover which would only happen if
the retry-logic failed first i.e both live and backup servers are unavailable.
I think failing over (and back) between different live/backup pairs in a
scenario like this make some sense, as long as it doesn't happen internally
within the groups. If not, would it make sense to add some additional check to
inhibit failback between live-backup-pairs?
I might have missed something with the topology listener though, it would
be nice to have this happen without having to "ping" the old node... but would
this work if the nodeID of the broker changes (say the broker cluster is part
of a blue/green deploy or similar, such that FQDN/IP remains the same but the
underlying broker is replaced by one started on a new journal)?
I can give that a try regardless, but it might take some time due to
vacation.
Br,
Anton
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
