You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@artemis.apache.org by Vilius Šumskas via users <us...@artemis.apache.org> on 2026/02/03 21:15:29 UTC
Critical Analyzer behaviour during startup/failover
Hello Justin,
finally had time during our maintenance to test this. You are right, critical analyzer doesn‘t stop the broker during slow startup now. It still produces thread dump, but startup completes. You can see this in the attached “startup of just primary.txt” where a primary of shared HA cluster (with backup turned off) was brought online with ~2,5GB of journal on a slow NFS volume.
What I probably was remembering previously is that HALT policy would still apply during failover operation. I have attached “backup failover.txt” logs from a backup of the same shared HA cluster, when I have stopped a primary for the maintenance.
IMHO critical analyzer should revert to LOG policy during failover too, if that state is possible to detect. Or better yet, maybe it is possible to detect that data is actually loaded from a journal but slowly, and ignore such slow journal operations in the critical analyzer completely?
--
Best Regards,
Vilius
From: Justin Bertram <jb...@apache.org>
Sent: Wednesday, January 7, 2026 11:41 PM
To: users@artemis.apache.org
Subject: Re: Artemis broker startup and pending messages impact
> I can get you standard analyzer logs with threaddump next time this happens, if you are interested.
I would definitely be interested in seeing that.
Justin
On Wed, Jan 7, 2026 at 3:21 PM Vilius Šumskas via users <us...@artemis.apache.org>> wrote:
It still kicks-in at least here. I don‘t remember the exact version I saw it last time, but it was a recent 2.3x or 2.4x version. We have a pretty slow NFS shared storage for journal. If we gather something like 2GB of dead lettered messages in the journal (tens of thousands of small messages), we usually unable to restart the broker without increasing default critical analyzer timeout.
I can get you standard analyzer logs with threaddump next time this happens, if you are interested.
--
Vilius
From: Justin Bertram <jb...@apache.org>>
Sent: Wednesday, January 7, 2026 6:36 PM
To: users@artemis.apache.org<ma...@artemis.apache.org>
Subject: Re: Artemis broker startup and pending messages impact
To clarify, the critical analyzer should not interfere with broker start-up. This was an issue in the past, but it was resolved via ARTEMIS-3664 [1].
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-3664