You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/08/04 19:42:00 UTC
[jira] [Work logged] (ARTEMIS-2868) Split Brain on Replication
could "damage" the Topology, isolating the server
[ https://issues.apache.org/jira/browse/ARTEMIS-2868?focusedWorklogId=466418&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-466418 ]
ASF GitHub Bot logged work on ARTEMIS-2868:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Aug/20 19:41
Start Date: 04/Aug/20 19:41
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request #3232:
URL: https://github.com/apache/activemq-artemis/pull/3232
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 466418)
Remaining Estimate: 0h
Time Spent: 10m
> Split Brain on Replication could "damage" the Topology, isolating the server
> ----------------------------------------------------------------------------
>
> Key: ARTEMIS-2868
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2868
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.14.0
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.15.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The issue is that after a split brain, during a reconnect the live broker will send a topology update to the live replacing the topology.
>
> As a result, new replicas will not be able to reconnect after the split brain, since the topology will return a wrong address, probably towards itself from backup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)