[
https://issues.apache.org/jira/browse/ARTEMIS-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578184#comment-17578184
]
ASF subversion and git services commented on ARTEMIS-3928:
----------------------------------------------------------
Commit 252e5b0b14231d80de6829e4cc5d5fc1a2df1ac1 in activemq-artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=252e5b0b14 ]
ARTEMIS-3928 Limiting parallel IO in paging which would allow multiple
destinations running all at once
Running HorizontalPagingTest with these variables would make the test to fail
unless these changes are applied.
export TEST_HORIZONTAL_SERVER_START_TIMEOUT=300000
export TEST_HORIZONTAL_TIMEOUT_MINUTES=120
export TEST_HORIZONTAL_PROTOCOL_LIST=OPENWIRE
export TEST_HORIZONTAL_OPENWIRE_DESTINATIONS=200
export TEST_HORIZONTAL_OPENWIRE_MESSAGES=1000
export TEST_HORIZONTAL_OPENWIRE_COMMIT_INTERVAL=100
export TEST_HORIZONTAL_OPENWIRE_RECEIVE_COMMIT_INTERVAL=0
export TEST_HORIZONTAL_OPENWIRE_MESSAGE_SIZE=20000
export TEST_HORIZONTAL_OPENWIRE_PARALLEL_SENDS=10
> Paging will flood memory with Native Buffers if too many destinations are
> used at once
> --------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3928
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3928
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.24.0
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.25.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There should be an IO limiter on the number of concurrent readings for Paging.
> Also if openwire is in use, there's no flow control what will also flood the
> queues with too much data and the broker will also OME.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
