It's probably waiting message redistribution to kick in...
I would recommend you to as much as you can to have a local consumer with clustering. Federation will play with consumer priorities and move the messages when you don't have enough load at the box and consumers in other nodes. I think it would play better. And ...if you give it a try... give it a feedback on the release please. There's a vote open for 2.7.0 on the dev list. On Fri, Mar 15, 2019 at 1:49 PM artemisn00b <[email protected]> wrote: > > So, I was testing my clustered setup (I have 3 nodes in a symmetric cluster > and I want all messages to be delivered to all nodes which have consumers), > and I was testing out large messages with a slow consumer. The situation I > ran into was - > > 1. I send lot of messages fast, and large to broker 1. > 2. My client is listening on broker 3, receiving the messages, but slow. I > added a sleep there. > 3. Now, a lot of messages get pages on broker 1, and I ungracefully shutdown > broker1. > 4. My producer reconnects, and moves to broker2. > 5. The client keeps receiving messages on broker3, but only the new ones. > The ones that were pages on broker1, won't be received. > 6. Now, even after I bring broker1 up live, the paged messages won't be > delivered to the consumer. > > I had to tear down the client and make it connect to broker1, to receive all > the paged messages. This is not something I can do in a production > environment. > > Do you guys have any solution to this as well? Would federated address > handle this in a different way? > > Thank you so much! > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html -- Clebert Suconic
