You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Liviu Citu (Jira)" <ji...@apache.org> on 2024/11/29 10:45:00 UTC
[jira] [Updated] (ARTEMIS-5189) [Artemis Failover] [Topic] [Non-Durable Consumer] Lost messages during failover switch
[ https://issues.apache.org/jira/browse/ARTEMIS-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liviu Citu updated ARTEMIS-5189:
--------------------------------
Summary: [Artemis Failover] [Topic] [Non-Durable Consumer] Lost messages during failover switch (was: [Artemis Failover] [Topics] [Non-Durable Consumers] Lost messages during failover switch)
> [Artemis Failover] [Topic] [Non-Durable Consumer] Lost messages during failover switch
> --------------------------------------------------------------------------------------
>
> Key: ARTEMIS-5189
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5189
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.38.0
> Reporter: Liviu Citu
> Priority: Critical
> Attachments: broker_backup.xml, broker_primary.xml
>
>
> Hi,
> I am currently migrating from Classic Broker to Artemis Broker and we also want to enable the Failover (Shared-Stored) switch.
> I have configured Artemis with Failover (Shared-Store) and during the failover switch, topic consumers loose events before reconnecting.
> When using durable consumers this is not happening so the problem (as expected) is only replicable for non-durable consumers.
>
> The reason for which we want to avoid using durable consumer is the performance impact on the broker side when there is a big number of messages and consumers for them.
> For a live client using Classic Broker we observed a big impact and slowness of the broker under high load (thousands of messages with more than 300 durable consumers).
> Indeed I am not able to test the same with Artemis broker as I do not have access to that environment however my expectation is that the Artemis broker will behave similarly.
>
> Is there a parameter in Artemis broker to make it wait a bit after the switch before dropping topic message, so that previous active consumers to have time to reconnect and consume the messages?
> Attached the Artemis Brokers Primary/Backup configuration.
> Thank you,
> Liviu
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact