activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martyn Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (ARTEMIS-473) Resolve split brain data after split brains scenarios.
Date Fri, 10 Mar 2017 12:24:04 GMT

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

Martyn Taylor reassigned ARTEMIS-473:
-------------------------------------

    Assignee: clebert suconic

> Resolve split brain data after split brains scenarios.
> ------------------------------------------------------
>
>                 Key: ARTEMIS-473
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-473
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 1.2.0
>            Reporter: Miroslav Novak
>            Assignee: clebert suconic
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> If master-slave pair is configured using replicated journal and there are no other servers
in cluster then if network between master and slave is broken then slave will activate. Depending
on whether clients were disconnected from master or not there might be or might not be failover
to slave. Problem happens in the moment when network between master and slave is restored.
Master and slave are active at the same time which is the split brain syndrom. Currently there
is no recovery mechanism to solve this situation.
> Suggested improvement: If clients failovered to slave then master will restart itself
so failback occurs (if configured). If clients did not failover and stayed connected to master
then backup will restart itself.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message