production clusters to 2.30.
>
> --
> Vilius
>
> -Original Message-
> From: Justin Bertram
> Sent: Friday, September 1, 2023 6:45 PM
> To: users@activemq.apache.org
> Subject: Re: There is a possible split brain on nodeID X after upgrade
> to 2.30
>
> How
unforeseen consequences before upgrading production
clusters to 2.30.
--
Vilius
-Original Message-
From: Justin Bertram
Sent: Friday, September 1, 2023 6:45 PM
To: users@activemq.apache.org
Subject: Re: There is a possible split brain on nodeID X after upgrade to
2.30
How
How is your cluster-connection configured? Are you using broadcast &
discovery groups? If so, I've seen instances of this when stopping and
starting the broker quickly. As far as I can tell the UDP multicast
datagram somehow is delivered back to the broker that sent it originally.
As long as your
Hi,
we have upgraded some of our environments from 2.28 to 2.30, others from 2.24
to 2.30 and all upgraded instances now show this strange log message during
live node restart cycle:
There is a possible split brain on nodeID 165c6eec-0429-11ed-a12a-42010a961402.
Topology update ignored
Full
