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 2017/12/15 13:58:00 UTC
[jira] [Commented] (ARTEMIS-1543) Vote on Live Setting causes
incorrectly shutdown when it's backup dies
[ https://issues.apache.org/jira/browse/ARTEMIS-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292555#comment-16292555 ]
ASF GitHub Bot commented on ARTEMIS-1543:
-----------------------------------------
GitHub user mtaylor opened a pull request:
https://github.com/apache/activemq-artemis/pull/1719
ARTEMIS-1543 Fix Quorum Vote with remain live setting
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mtaylor/activemq-artemis ARTEMIS-1543
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1719.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1719
----
commit 84b0c2f7d52d156707bda2899b0635a58674b518
Author: Martyn Taylor <mt...@redhat.com>
Date: 2017-12-08T12:47:03Z
ARTEMIS-1543 Fix Quorum Vote with remain live setting
----
> Vote on Live Setting causes incorrectly shutdown when it's backup dies
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-1543
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1543
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Martyn Taylor
> Assignee: Martyn Taylor
> Priority: Critical
>
> The HA replication functionality has the ability to configure the live to request quorum from other nodes in the cluster for it to stay live should it's back up fail. The intent here is prefer the loss of availability over a potential split brain situation should a live and backup become partitoned. However, this causes the live to incorrectly shutdown should it's backup die and no partition experienced.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)