[
https://issues.apache.org/jira/browse/ARTEMIS-3664?focusedWorklogId=718144&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-718144
]
ASF GitHub Bot logged work on ARTEMIS-3664:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 31/Jan/22 18:33
Start Date: 31/Jan/22 18:33
Worklog Time Spent: 10m
Work Description: clebertsuconic merged pull request #3935:
URL: https://github.com/apache/activemq-artemis/pull/3935
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 718144)
Remaining Estimate: 0h
Time Spent: 10m
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
