[
https://issues.apache.org/jira/browse/ARTEMIS-3178?focusedWorklogId=842360&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-842360
]
ASF GitHub Bot logged work on ARTEMIS-3178:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Jan/23 18:14
Start Date: 30/Jan/23 18:14
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on code in PR #4349:
URL: https://github.com/apache/activemq-artemis/pull/4349#discussion_r1090981753
##########
artemis-server/src/main/resources/schema/artemis-configuration.xsd:
##########
@@ -4000,6 +4000,23 @@
</xsd:annotation>
</xsd:element>
+ <xsd:element name="page-limit-bytes" type="xsd:string"
default="-1" maxOccurs="1" minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ After the address entering into page mode, this attribute
will configure how many pages can be written into page before activating the
page-full-policy.
Review Comment:
thanks Tim
Issue Time Tracking
-------------------
Worklog Id: (was: 842360)
Time Spent: 2h (was: 1h 50m)
> 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
> 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)
