activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbertram <...@git.apache.org>
Subject [GitHub] activemq-artemis pull request #1026: ARTEMIS-978 replicating live restarts a...
Date Fri, 17 Feb 2017 18:56:14 GMT
GitHub user jbertram opened a pull request:

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

    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.

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

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-978

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

    https://github.com/apache/activemq-artemis/pull/1026.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 #1026
    
----
commit 5bd198043850ec64c68e9bf0659543b9aebd90b6
Author: Justin Bertram <jbertram@apache.org>
Date:   2017-02-15T15:19:30Z

    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.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message