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

Posted to issues@activemq.apache.org by "Francesco Nigro (Jira)" <ji...@apache.org> on 2022/03/07 12:16:00 UTC

[jira] [Updated] (ARTEMIS-3703) Block clients until coordinated sequence is advanced after backup drop

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

Francesco Nigro updated ARTEMIS-3703:
-------------------------------------
    Description: 
With pluggable quorum vote, if the backup connection drop, live can serve clients unreplicated while not yet incremented activation sequence: this can lead to inconsistency if the unreplicated live will crash *before* it, causing the replica to be able to become live, but with some missing data.

 

  was:
With pluggable quorum vote, if the backup connection drop, live can serve clients unreplicated while not yet incremented activation sequence: this can lead to inconsistency if the unreplicated live will crash *before* it. 

A backup with that same activation sequence can start and become live even if the just crashed live data is different.

 

 


> Block clients until coordinated sequence is advanced after backup drop
> ----------------------------------------------------------------------
>
>                 Key: ARTEMIS-3703
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3703
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Francesco Nigro
>            Assignee: Domenico Francesco Bruscino
>            Priority: Major
>
> With pluggable quorum vote, if the backup connection drop, live can serve clients unreplicated while not yet incremented activation sequence: this can lead to inconsistency if the unreplicated live will crash *before* it, causing the replica to be able to become live, but with some missing data.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)