[
https://issues.apache.org/jira/browse/ARTEMIS-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-3298.
-------------------------------------
Resolution: Abandoned
> CriticalAnalyzer alert with replication and many clients
> --------------------------------------------------------
>
> Key: ARTEMIS-3298
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3298
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Attachments: storage_manager_crash.log
>
>
> While performing load testing with a single pair broker, the critical
> analyzer kick-in on master broker, shutting it down.
> The broker version used is
> https://github.com/apache/activemq-artemis/commit/fe361d3faeba0a8ff12f16a8fed45bb39d4c6cbd
> Next runs are performed using by switching to LOG policy to understand if the
> issue is legit or not.
> On a 16 cores client machine, the critical number of producers/consumers
> seems 16-16, sending durable 100 bytes messages.
> The journal configuration (for both master and slave) is MAPPED without
> datasync.
> I'm going to update the description as soon as I try with other journal
> configurations.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
