You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "yangwei (JIRA)" <ji...@apache.org> on 2018/07/05 09:47:00 UTC
[jira] [Updated] (ARTEMIS-1966) Replication channel closed but not
connection if flow controlled during replication
[ https://issues.apache.org/jira/browse/ARTEMIS-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
yangwei updated ARTEMIS-1966:
-----------------------------
Description:
We use SharedNothing Activation. If flow control occurs during replication, replication channel would be closed and enabled flag is set to false. After it, the message would not be sent to backup node. If live server crashes at this time, the backup node will fail over, resulting in data loss.
So we close connection if flow controlled, then backup node would be signaled failure replicating and restart server.
was:If flow control occurs during replication, replication channel would be closed and enabled flag is set to false. After it, the message would not be sent to backup node. If live server crashes, the backup node will fail over, resulting in data loss.
> Replication channel closed but not connection if flow controlled during replication
> -----------------------------------------------------------------------------------
>
> Key: ARTEMIS-1966
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1966
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.6.2
> Reporter: yangwei
> Priority: Major
>
> We use SharedNothing Activation. If flow control occurs during replication, replication channel would be closed and enabled flag is set to false. After it, the message would not be sent to backup node. If live server crashes at this time, the backup node will fail over, resulting in data loss.
> So we close connection if flow controlled, then backup node would be signaled failure replicating and restart server.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)