It should still work with redistribution, but that will only happen as it consume message from the broker..
if you have a bunch of messages stuck on the current broker.. it won't move scanning for redistribution unless you clear space in memory. I think that's documented. you should probably avoid a slow / stuck consumer on this case. On Wed, Oct 14, 2020 at 11:17 AM gaetan caumartin <[email protected]> wrote: > > Hello, > > I opened the following ticket at the beginning of september: > https://issues.apache.org/jira/browse/ARTEMIS-2894 > > My goal is to replace our ActiveMQ 5 network of Brokers with artemis. > > I started to work on it with artemis 2.9.0 and then 2.11.0. and successffully > configured a network of broker with the equivalent of the > replayWhenNoConsumer (the redistribution with redistributionDelay=0) > > The problem is that since 2.12, this don't work anymore when we accumulate > many messages on a broker and trigger the paging. > When a consumer is connected on another member of the Network of broker, the > redistribution starts but all the messages are not transferred and most > disappeared. > They seem to be stucked in a destination used for clustering when the paging > occured on it too > (internal.sf.my-cluster.335036cc-edc0-11ea-bae1-005056a7672b for example) > > I can't find what have caused this since the 2.12 so if someone with more > knowledge of the paging and clustering can help me it would be great. > > Regards, > Gaetan > > -- Clebert Suconic
