[
https://issues.apache.org/jira/browse/ARTEMIS-3557?focusedWorklogId=686569&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-686569
]
ASF GitHub Bot logged work on ARTEMIS-3557:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Nov/21 16:26
Start Date: 25/Nov/21 16:26
Worklog Time Spent: 10m
Work Description: gtully commented on pull request #3858:
URL: https://github.com/apache/activemq-artemis/pull/3858#issuecomment-979342527
@AntonRoskvist apologies for the delay in response. What was in my mind is
the auto create queue case, where the binding is created as part of consumer
creation, and on the server that is a two step process, create queue/binding
and add consumer. With OFF, any message produced will go to the queue/binding
and if the redistributor gets there with a 0 delay, the message may be gone!
With the maxHops - potentially never to come back. That window may be very
small or maybe there is sufficient sync in there to eliminate it... I don't
know for sure. I will need a run in the debugger with a test!
remind me, what is the use case that causes a binding to be created at
runtime if not as part of add consumer?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 686569)
Time Spent: 2h 10m (was: 2h)
> ARTEMIS-1925 fix does not handle redistribution to "old" consumers
> ------------------------------------------------------------------
>
> Key: ARTEMIS-3557
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3557
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> OFF_WITH_REDISTRIBUTION does not handle this scenario:
> If a destination and consumer exist on one node in a cluster and a producer
> shows up on another node messages will not get redistributed until the old
> consumer disconnects and reconnects.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
