[
https://issues.apache.org/jira/browse/ARTEMIS-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573008#comment-17573008
]
ASF subversion and git services commented on ARTEMIS-3805:
----------------------------------------------------------
Commit 7184862bb54f50f524a2a5b457a1afd68d1f95ab in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7184862bb5 ]
NO-JIRA update XSD missed in ARTEMIS-3805
> Change default Bridge Producer Window Size to 1MB
> -------------------------------------------------
>
> Key: ARTEMIS-3805
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3805
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.22.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The default producer value for a Bridge (clustered or not) is -1, meaning
> unlimited.
> We had seen scenarios where the target and source runs out of memory when
> running on slow networking or disk.
> I have looked into changing the implementation to back pressure the
> networking, however values are added into an Executor (through an Actor), and
> we the alternate back pressure would mean to add a new value to this
> executor, binding it towards the network.
> Which is a whole circle round back to the same problem... managing credits.
> instead of adding a new value, I will change the default value for Bridges
> which would have the same impact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
