Ok, I agree based on a cursory reading of that patch. The extra ackReason defaults to normal in one direction and isn’t read in the other direction. Killed, replaced, and expired being interpreted as normal just means that the 2.20 bugs will persist until both sides are updated.
I’ll test it out with different version docker containers. I suppose as far as writing tests you mean something like the MultiVersionReplicaTest. Stephen E. Baker From: Clebert Suconic <clebert.suco...@gmail.com> Date: Tuesday, October 11, 2022 at 12:59 PM To: users@activemq.apache.org <users@activemq.apache.org> Subject: Re: Mirror compatibility across versions In theory it should work. Only change that might break compatibility is https://github.com/apache/activemq-artemis/commit/68f6d8263d8c795722805f0e4d6939e7a8b9ed48 which is ARTEMIS-3743 / ARTEMIS-3766 Use ACKReason on Mirror to determine target operations and fixing Delivering statistics on Mirror I tried to not break compatibility, but I just realized we should add a test to validate compatibility between mirrors. so, I will say it should be compatible, but I would test it before doing it in the real system. if you are willing to contribute to a compatibility test :) On Tue, Oct 11, 2022 at 10:06 AM Stephen Baker <stephen.ba...@rmssoftwareinc.com> wrote: > > We are planning our production upgrade from 2.20 to 2.25. These upgrades > involve a loss of service in the window between stopping the live and when > the backup instance becomes ready to process messages. > > I was wondering if the mirror protocol is expected to be compatible between > those versions. If so we could upgrade our cold site, and then wait for a > planned failover to avoid any additional down time. I know that quite a bit > of work was done by Clebert in 2.24 so I was hoping he could weigh in. > > Stephen E Baker -- Clebert Suconic [EXTERNAL]: This email originated from outside of Rave Mobile Safety. Do not click links or open attachments unless you recognize the sender and know the content is safe.
