[
https://issues.apache.org/jira/browse/ARTEMIS-4378?focusedWorklogId=878180&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-878180
]
ASF GitHub Bot logged work on ARTEMIS-4378:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Aug/23 14:19
Start Date: 24/Aug/23 14:19
Worklog Time Spent: 10m
Work Description: gtully opened a new pull request, #4590:
URL: https://github.com/apache/activemq-artemis/pull/4590
…ured as pull, consumerWindowSize=0
Issue Time Tracking
-------------------
Worklog Id: (was: 878180)
Remaining Estimate: 0h
Time Spent: 10m
> Federation, ignore address policy when using pull consumer connection
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-4378
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4378
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Federation
> Affects Versions: 2.29.0
> Reporter: Gary Tully
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Using the batching pull consumer from ARTEMIS-4314 is only applicable to
> queue Federation but both policies can be configured in the same federation.
> If consumer window size of zero is configured any address policy should be
> ignored. With address federation there is no local queue to gauge capacity
> and messages will just accumate in the upstream. The concept of a pull
> consumer for address federation does not make any sense.
> This strategy is already adopted for queue Federation configured for
> multicast addresses.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
