You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/06/22 14:45:00 UTC
[jira] [Work logged] (ARTEMIS-6008) Critical Analyzer should not kick in during Failover phase of the broker
[ https://issues.apache.org/jira/browse/ARTEMIS-6008?focusedWorklogId=1026263&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1026263 ]
ASF GitHub Bot logged work on ARTEMIS-6008:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Jun/26 14:44
Start Date: 22/Jun/26 14:44
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #6533:
URL: https://github.com/apache/artemis/pull/6533#issuecomment-4769525824
I think instead of checking the server state you could just check `ActiveMQServer#isActive` and that would work for both the primary and the backup use-cases and you wouldn't need to add another field. What do you think?
Issue Time Tracking
-------------------
Worklog Id: (was: 1026263)
Remaining Estimate: 0h
Time Spent: 10m
> Critical Analyzer should not kick in during Failover phase of the broker
> ------------------------------------------------------------------------
>
> Key: ARTEMIS-6008
> URL: https://issues.apache.org/jira/browse/ARTEMIS-6008
> Project: Artemis
> Issue Type: Bug
> Reporter: Vilius Šumskas
> Priority: Major
> Labels: pull-request-available
> Attachments: backup failover.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://issues.apache.org/jira/browse/ARTEMIS-3664 fixed an issue with Critical Analyzer killing the broker during slow startup. However, during live/backup pair failover Critical Analyzer still kicks in on the backup.
> I think 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?
> Attached is a thread dump produced during failover operation on backup Artemis node, which was trying to pull in 2GB journal from slow NFS volume.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org