[
https://issues.apache.org/jira/browse/ARTEMIS-4084?focusedWorklogId=824440&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-824440
]
ASF GitHub Bot logged work on ARTEMIS-4084:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Nov/22 07:54
Start Date: 09/Nov/22 07:54
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4281:
URL:
https://github.com/apache/activemq-artemis/pull/4281#issuecomment-1308349850
Very interesting!
I think the issues comes down to the transaction getting handled as two
consecutive rollbacks for some reason... logging out refs.size() in QueueImpl
shows that the first run rolls back some 90% of all messages and this is really
fast... then the rest of the messages gets rolled back and I believe these
arrive out of order such that the list has to be scanned for each message to
find it's proper place...
And yes, I believe the CriticalAnalyzer is absolutely right to stop the
broker. In fact I tried to set it to LOG and the broker was never able to
recover properly... or at least not for some 30 minutes which is how much time
I gave it before manually restarting.
Issue Time Tracking
-------------------
Worklog Id: (was: 824440)
Time Spent: 3h 10m (was: 3h)
> Rollbacking massive amounts of messages might crash broker
> ----------------------------------------------------------
>
> Key: ARTEMIS-4084
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4084
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Critical Analyzer triggers, but even if it is set to LOG or disabled the
> broker is put in such a bad state it becomes unresponsive until restarted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
