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

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

Github user clebertsuconic commented on a diff in the pull request:

    https://github.com/apache/activemq-artemis/pull/513#discussion_r62853199
  
    --- Diff: 
artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/ActiveMQServerImpl.java
 ---
    @@ -674,6 +674,26 @@ public void setJMSQueueDeleter(QueueDeleter 
jmsQueueDeleter) {
           this.jmsQueueDeleter = jmsQueueDeleter;
        }
     
    +   @Override
    +   public boolean isInitialReplicationSynchronizationComplete() {
    --- End diff --
    
    suggestion: wouldn't isReplicaSync be a better name?


> 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
>             Fix For: 1.3.0
>
>
> 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