activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-978) Replicating live restarts as backup when both live and backup are killed in a cluster
Date Fri, 17 Feb 2017 21:13:42 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872528#comment-15872528
] 

ASF subversion and git services commented on ARTEMIS-978:
---------------------------------------------------------

Commit 5bd198043850ec64c68e9bf0659543b9aebd90b6 in activemq-artemis's branch refs/heads/master
from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=5bd1980 ]

ARTEMIS-978 replicating live restarts as backup

In a cluster of replicated live/backup pairs if a backup crashes and
then its live crashes the cluster will retain the topology information
of the live such that when the live server restarts it will check the
cluster to see if its nodeID is present (which it will be) and then it
will activate as a backup rather than a live. To prevent this situation
an additional check is necessary to see if the server with the matching
nodeID is actually active or not which is done by attempting to make a
connection to it.


> Replicating live restarts as backup when both live and backup are killed in a cluster
> -------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-978
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-978
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.5.2
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>             Fix For: 2.0.0
>
>




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

Mime
View raw message