Scaling down is different. It is an intentional, graceful procedure oftentimes initiated administratively. The broker scaling down will explicitly create the queues on the target broker if they don't exist. Then it will transfer all message and transaction data to the target broker. This is like dynamically turning one of the other live brokers in the cluster into a slave, and it enables a kind of fail-over for clients which are connected to the scaling down node.
That process isn't at all like what happens during a catastrophic node failure where there's no chance for the broker to take any action. Justin On Fri, Apr 17, 2020 at 2:16 PM AntonR <anton.roskv...@volvo.com> wrote: > Hmm, I might have the semantics mixed up here but... How does clients > behave > in a dynamically scaling performance cluster then? Clients that join the > cluster during high load can't possibly stop working after the broker they > originally connected to scales down and stops, right? > > Doesn't a "failover" happen to a broker that is still available? And if it > does, can't that same logic also be used as a "failover" in the sense that > OP is asking about? > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html > >
