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 subversion and git services (Jira)" <ji...@apache.org> on 2022/01/31 18:34:00 UTC
[jira] [Commented] (ARTEMIS-3664) Critical Analyzer should not kick in during Starting phase of the broker
[ https://issues.apache.org/jira/browse/ARTEMIS-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484852#comment-17484852 ]
ASF subversion and git services commented on ARTEMIS-3664:
----------------------------------------------------------
Commit ba02fccb77539f8642aa5d09511cda2fc998542e in activemq-artemis's branch refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ba02fcc ]
ARTEMIS-3664 Critical Analyzer should not HALT or STOP the broker during the startup
> Critical Analyzer should not kick in during Starting phase of the broker
> ------------------------------------------------------------------------
>
> Key: ARTEMIS-3664
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3664
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.20.0, 2.19.1
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.21.0
>
>
> Say the journal is too big to be loaded in less than 2 minutes or the CPU is not powerful enough... anything...
> the system should not give up loading the journal.. and it should not HALT the startup of the broker. Up to that point it should instead just log.warn.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)