You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2019/04/26 01:20:00 UTC

[jira] [Closed] (ARTEMIS-455) Master does not create new backup when colocated server fails

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

clebert suconic closed ARTEMIS-455.
-----------------------------------
    Resolution: Won't Fix

I wouldn't use colocated on your case.

Your description is a bit incomplete and I couldn't figure out how to replicate it.

 

 

> Master does not create new backup when colocated server fails
> -------------------------------------------------------------
>
>                 Key: ARTEMIS-455
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-455
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.2.0
>            Reporter: Brandon Breuil
>            Priority: Critical
>
> When using a colocated backup configuration with replication, the master server does not recreate backups if the node that contained the original backup fails. This leaves one master node in the cluster with no replica.
> How to reproduce:
> 1) Create 2 servers with a colocated replication ha policy (a master and backup node will be created on each server)
> 2) Kill one of the servers
> 3) Create a new server with the same ha policy
> 4) The original master does not re-create a backup node on the new server



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)