You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2021/10/12 00:52:00 UTC

[jira] [Resolved] (ARTEMIS-3429) Backup forget coordination-id after quorum loss

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

Justin Bertram resolved ARTEMIS-3429.
-------------------------------------
    Fix Version/s: 2.19.0
       Resolution: Fixed

> Backup forget coordination-id after quorum loss
> -----------------------------------------------
>
>                 Key: ARTEMIS-3429
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3429
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.18.0
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Major
>             Fix For: 2.19.0
>
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> Assuming a multi-primary set-up, if the broker acting as backup lost quorum, is restarted without applying the coordination-id patching on NodeManager:  if its local activation sequence is > 0 (because of a past sync with the other live) the backup succeed to activate, causing a split-brain (although its NodeID is a random one vs the original coordination-id).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)