activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1654) Bridge reconnect broken
Date Fri, 02 Feb 2018 17:19:00 GMT


ASF subversion and git services commented on ARTEMIS-1654:

Commit 032210a7c692d26baa13a80f30a3cf62c5df594e in activemq-artemis's branch refs/heads/master
from [~andytaylor]
[;h=032210a ]

ARTEMIS-1654 - fix brige reconnect logic

Make sure that if a bridge disconnects and there is no record in the topology that it uses
the original bridge connector to reconnect.

Originally the live broker that disconnected was left in the Topology, thie broke quorum voting
as when th evote happened all brokers when asked though th etarget broker was still alive.
The fix for this was to remove the target live broker from the Topology. Since the bridge
reconnect logic relied on this in a non HA environment to reconnect this stopped working.
The fix now uses the original target connector (or backup) to reconnect in the case where
the broker was actually removed from the cluster.

> Bridge reconnect broken
> -----------------------
>                 Key: ARTEMIS-1654
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Andy Taylor
>            Assignee: Andy Taylor
>            Priority: Major
> A quorum fix broker this. Originally we used to leave a node in th etopology when it
disconnected, this broke voting as all brokers thought a crashed live was still around. The
bridge reconnect logic relied on this so now it needs to fall back to the originall connectors
if no backup is available and the live is lost.

This message was sent by Atlassian JIRA

View raw message