[
https://issues.apache.org/jira/browse/ARTEMIS-5338?focusedWorklogId=960855&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-960855
]
ASF GitHub Bot logged work on ARTEMIS-5338:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Mar/25 20:41
Start Date: 07/Mar/25 20:41
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #5546:
URL:
https://github.com/apache/activemq-artemis/pull/5546#issuecomment-2707405503
I am adding another related commit into this, exposing the number of
records...
I almost squashed it into the same commit to be honest but since these are
separate JIRAs I am keeping it separate.
if anyone prefers to be squashed I can do it.
Issue Time Tracking
-------------------
Worklog Id: (was: 960855)
Time Spent: 50m (was: 40m)
> Flow control between Mirror Target and AckManager's size
> --------------------------------------------------------
>
> Key: ARTEMIS-5338
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5338
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.39.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.40.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Say a mirror is feeding ack retries... if the mirror is feeding acks faster
> than the target can process you could get to a situation where you would get
> a OME as you were not able to sustain the load.
> The server should verify if the number of pending records is bellow a certain
> configured threshold and credits should not be issues to the sender while the
> threshold is too high.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
