[
https://issues.apache.org/jira/browse/ARTEMIS-3178?focusedWorklogId=842393&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-842393
]
ASF GitHub Bot logged work on ARTEMIS-3178:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Jan/23 23:19
Start Date: 30/Jan/23 23:19
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4349:
URL:
https://github.com/apache/activemq-artemis/pull/4349#issuecomment-1409508147
all the comments are resolved.. tests are 100%... I'm merging this...
if anyone sees anything else wrong I will send a new PR.. (or feel free to
send any adjustments yourself of course).
Issue Time Tracking
-------------------
Worklog Id: (was: 842393)
Time Spent: 2h 40m (was: 2.5h)
> Provide a way to limit the size of an address after paged
> ---------------------------------------------------------
>
> Key: ARTEMIS-3178
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3178
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker, Configuration
> Affects Versions: 2.17.0
> Reporter: Gary Tully
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.28.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> I am adding three attributes to Address-settings:
> * page-limit-bytes: Number of bytes. We will convert this metric into max
> number of pages internally by dividing max-bytes / page-size. It will allow a
> max based on an estimate.
> * page-limit-messages: Number of messages
> * page-full-message-policy: fail : drop
> We will now allow paging, until these max values and then fail or drop
> messages.
> Once these values are retracted, the address will remain full until a period
> where cleanup is kicked in by paging. So these values may have a certain
> delay on being applied, but they should always be cleared once cleanup
> happened.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
