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 2022/04/04 21:23:00 UTC
[jira] [Work logged] (ARTEMIS-3753) Messages are not deleted in the mirror broker if they were distributed from the main to another broker in the cluster
[ https://issues.apache.org/jira/browse/ARTEMIS-3753?focusedWorklogId=752513&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-752513 ]
ASF GitHub Bot logged work on ARTEMIS-3753:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Apr/22 21:22
Start Date: 04/Apr/22 21:22
Worklog Time Spent: 10m
Work Description: iliya-gr opened a new pull request, #4012:
URL: https://github.com/apache/activemq-artemis/pull/4012
In cluster configuration messages could be routed to internal queues for
further delivering on different broker. We need to check that before
sending to SNF, otherwise message can stuck on target server and will
never receive ACK.
Issue Time Tracking
-------------------
Worklog Id: (was: 752513)
Remaining Estimate: 0h
Time Spent: 10m
> Messages are not deleted in the mirror broker if they were distributed from the main to another broker in the cluster
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3753
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3753
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.19.1, 2.21.0
> Environment: JDK 8
> JDK 11
> Windows 10
> Ubuntu 20.04
> Reporter: Mikhail Lukyanov
> Priority: Major
> Attachments: ArtemisClusterMirror.rar, brokerA1.xml, brokerA2.xml, brokerB1.xml, image-2022-04-01-18-04-36-472.png, image-2022-04-01-18-04-42-130.png, image-2022-04-01-18-05-12-973.png, image-2022-04-01-18-05-27-639.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When testing [Mirroring|https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html#mirroring], I found that it works unstable for brokers that are in a cluster. Messages are not deleted in the mirror broker if they were distributed ([_*initial distribution*_ and *_redistribution_*|https://activemq.apache.org/components/artemis/documentation/latest/clusters.html] too) from the main to another broker in the cluster.
> I have the following scheme, brokers A1 and A2 into clusters and A1 has mirror B1.
> *Steps*
> # Create 3 brokers (A1, A2, B1) with default user (root) and password (root) by _artemis create_
> # Replace their configuration with the configuration from the attachment (brokerA1.xml and etc.)
> # Run this brokers _artemis run_
> # Run ArtemisConsumer from maven project ArtemisClusterMirror.rar in attachment
> # Run ArtemisProducer from maven project ArtemisClusterMirror.rar in attachment
> # Wait for the producer to finish
> # Turn off consumer
> # Compare the number of messages queue Q1 in brokers A1 and B1
> *Expected Behavior:*
> The number of messages in the queue Q1 is the same (0), it is empty
> *Received Behavior:*
> The queue Q1 in mirror broker B1 contains 50 messages that were sent by the producer. There were no signals to delete these messages from broker A1 when moving them to another cluster broker A2 (with consumer). Screenshots in attachment.
> It is also not clear why the internal cluster queues with the _notif_ prefix are mirrored, in theory they should not. They also often contain messages that are not in the main broker.
> !image-2022-04-01-18-04-42-130.png!
> !image-2022-04-01-18-05-12-973.png!
> !image-2022-04-01-18-05-27-639.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)