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

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

GitHub user jbertram opened a pull request:

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

    ARTEMIS-517

    

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

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

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

    https://github.com/apache/activemq-artemis/pull/513.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 #513
    
----
commit 628b0d5a7bd96f9dc5b5a894860417ac16378682
Author: jbertram <[email protected]>
Date:   2016-05-06T19:53:55Z

    ARTEMIS-517

----


> Provide public API method to check whether backup is synchronized with live 
> server 
> -----------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-517
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-517
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 1.2.0
>            Reporter: Miroslav Novak
>            Assignee: Justin Bertram
>
> If HA is configured with replicated journal then it takes some time to backup 
> to synchronize with live server.  Once backup is in sync with live then 
> following information appears in server.log:
> {code}
> 13:20:00,739 INFO  [org.apache.activemq.artemis.core.server] (Thread-3 
> (ActiveMQ-client-netty-threads-457000966)) AMQ221024: Backup server 
> ActiveMQServerImpl::serverUUID=bc015b34-fd73-11e5-80ca-1b35f669abb8 is 
> synchronized with live-server.
> 13:20:01,500 INFO  [org.apache.activemq.artemis.core.server] (Thread-2 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@41f992ab-83559664))
>  AMQ221031: backup announced
> {code}
> Reading server logs to see whether backup is in sync is not convenient and 
> user friendly way. 
> We should provide public API to check state of synchronization. It should be 
> added to {{Activation}} interface. 
> This method should be implemented for {{SharedNothingBackupActivation}} and 
> also {{SharedNothingLiveActivation}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to