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 2016/06/06 20:30:21 UTC

[jira] [Commented] (ARTEMIS-552) Stopping Replication Target may take live irresponsive for some time

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

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

GitHub user clebertsuconic opened a pull request:

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

    ARTEMIS-552 Replication target being finished can lead to instability

    

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

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

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

    https://github.com/apache/activemq-artemis/pull/563.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 #563
    
----
commit 2e6586548b3a0d69f1ce2079a2da243af16a28c6
Author: Clebert Suconic <cl...@apache.org>
Date:   2016-06-01T19:34:57Z

    ARTEMIS-552 Replication target being finished can lead to instability on live
    
    https://issues.apache.org/jira/browse/ARTEMIS-552

----


> Stopping Replication Target may take live irresponsive for some time
> --------------------------------------------------------------------
>
>                 Key: ARTEMIS-552
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-552
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: clebert suconic
>             Fix For: 1.3.0
>
>
> Stopping a target replication may set the live server irresponsive for some time.
> i - Ping checks can be interrupted due to flow control between live and backup
> ii - Duplicate cache may be delayed, if the client reconnects the server may ignore duplicate caches. the entry has to be added immediately without waiting a replication roundtrip.



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