[
https://issues.apache.org/jira/browse/ARTEMIS-2654?focusedWorklogId=402190&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-402190
]
ASF GitHub Bot logged work on ARTEMIS-2654:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Mar/20 14:10
Start Date: 12/Mar/20 14:10
Worklog Time Spent: 10m
Work Description: michaelpearce-gain commented on issue #3015:
ARTEMIS-2654 Improving Page cleanup and Operation Context
URL: https://github.com/apache/activemq-artemis/pull/3015#issuecomment-598206055
so the simulation test, was a way we re-created what occured in prod,
basically we had a massive volatilty in the market meaning alot of messages
burst into the session, it took a we while for consumers to scale up causing to
page, but then consumers kept pace, but then we found we had some blocked flows.
Note the recreator basically is a way we've found to re-create the problem,
i expect in issues like this decreased perfomance but i dont expect it to stop
and block.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 402190)
Time Spent: 3h (was: 2h 50m)
> Improve Paging.Stop cleanup
> ---------------------------
>
> Key: ARTEMIS-2654
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2654
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.11.0
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> There's a Blocking operation on Page.stopPaging and cleanup should use its
> own OperationContext.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
