You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2024/08/21 09:43:00 UTC

[jira] [Updated] (ARTEMIS-4986) Replication/Vote incompatibility between versions up to 2.31.2 (inclusive) and 2.32.0 - 2.36.0

     [ https://issues.apache.org/jira/browse/ARTEMIS-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell updated ARTEMIS-4986:
------------------------------------
    Summary: Replication/Vote incompatibility between versions up to 2.31.2 (inclusive) and 2.32.0 - 2.36.0  (was: Replication/Vote incompatibility between any version up to 2.31.2 (inclusive) and 2.32+)

> Replication/Vote incompatibility between versions up to 2.31.2 (inclusive) and 2.32.0 - 2.36.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4986
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4986
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.32.0, 2.33.0, 2.34.0, 2.35.0, 2.36.0
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>             Fix For: 2.37.0
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> The change for "ARTEMIS-3474 replace non-inclusive terms" in 2.32.0 changed a String that was used on the wire for Voting. That string is sent on the Vote packet, and so created an incompatibility if mixing a broker <= 2.31.2 with those of versions 2.32.0 - 2.36.0 (e.g during a rolling upgrade) where they dont understand each others values. The other nodes would fail with the following message:
> AMQ224090: This node is not configured for Quorum Voting, all nodes must be configured for HA
> The server will simply not respond the VoteRequest on that case and the blockCall timeout will fail.
> To fix this I'm making 2.37.0+ understand both string values, and when voting against < 2.37.0 versions applying a shorter timeout that will just be ignored and cause retry with the older packet and similar short timeout in case the response wasn't found, before trying for the full timeout with the current value.
> The wire version will be bumped in 2.37.0 such that this process does not occur against other new 2.37.0+ brokers, which will then be known to understand the new value (and now old value).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact