[
https://issues.apache.org/jira/browse/ARTEMIS-2214?focusedWorklogId=183803&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-183803
]
ASF GitHub Bot logged work on ARTEMIS-2214:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 10/Jan/19 16:54
Start Date: 10/Jan/19 16:54
Worklog Time Spent: 10m
Work Description: franz1981 commented on issue #2482: ARTEMIS-2214 Cache
durable&deliveryTime in PagedReference
URL: https://github.com/apache/activemq-artemis/pull/2482#issuecomment-453169452
Please due to a change can you rebase this one?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 183803)
Time Spent: 10m
Remaining Estimate: 0h
> ARTEMIS-2214 Cache durable&deliveryTime in PagedReference
> ---------------------------------------------------------
>
> Key: ARTEMIS-2214
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2214
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.6.3
> Reporter: Qihong Xu
> Priority: Major
> Attachments: stacks.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We recently performed a test on artemis broker and found a severe performance
> issue.
> When paged messages are being consumed, decrementMetrics in
> QueuePendingMessageMetrics will try to ‘getMessage’ to check whether they are
> durable or not. In this way queue will be locked for a long time because page
> may be GCed and need to be reload entirely. Other operations rely on queue
> will be blocked at this time, which cause a significant TPS drop. Detailed
> stacks are attached below.
> This also happens when consumer is closed and messages are pushed back to the
> queue, artemis will check priority on return if these messages are paged.
> To solve the issue, durable and priority need to be cached in PagedReference
> just like messageID, transactionID and so on. I have applied a patch to fix
> the issue. Any review is appreciated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
