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

ASF GitHub Bot commented on ARTEMIS-473:
----------------------------------------

GitHub user clebertsuconic opened a pull request:

    https://github.com/apache/activemq-artemis/pull/895

    ARTEMIS-473/ARTEMIS-863 Detect network failures

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/clebertsuconic/activemq-artemis netcheck

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/895.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 #895
    
----
commit 5d040c41822cbda784c29c6488073e5dff4d6f13
Author: Clebert Suconic <clebertsuco...@apache.org>
Date:   2016-11-17T15:01:31Z

    ARTEMIS-473/ARTEMIS-863 Detect network failures

----


> 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
>            Priority: Critical
>             Fix For: 1.6.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.4#6332)

Reply via email to