Where exactly do you see the re-ordering of messages and how are you determining that they are, in fact, re-ordered? Are they re-ordered in the target queue itself or on the consumer(s)? Do you have a way that I can reproduce this behavior?
If I recall correctly there is just one thread that forwards messages from the internal store-and-forward queue to the target node so I don't think that would be the reason for this behavior. Justin On Fri, May 3, 2024 at 10:02 AM Dondorp, Erwin <erwin.dond...@ns.nl.invalid> wrote: > Intern > > Hello, > > I have an Artemis cluster with several nodes. > In many cases, messages arrive on one node and are consumed from another > node. > The cluster-connections between the nodes do their work to make that > happen. > > But under high-load we see messages being re-ordered between the > broker-nodes, and I am trying to minimize (or eliminate) that effect. > The re-ordering is usually only within a small set of messages, e.g. > within a set of 10 to 20 messages. > My assumption is that this is due to the use of multiple threads in the > cluster-connections when there are a lot of messages. > Is there a way to have more control over this? > > thx! > Erwin > > ________________________________ > > Deze e-mail, inclusief eventuele bijlagen, is uitsluitend bestemd voor > (gebruik door) de geadresseerde. De e-mail kan persoonlijke of > vertrouwelijke informatie bevatten. Openbaarmaking, vermenigvuldiging, > verspreiding en/of verstrekking van (de inhoud van) deze e-mail (en > eventuele bijlagen) aan derden is uitdrukkelijk niet toegestaan. Indien u > niet de bedoelde geadresseerde bent, wordt u vriendelijk verzocht degene > die de e-mail verzond hiervan direct op de hoogte te brengen en de e-mail > (en eventuele bijlagen) te vernietigen. > > Informatie vennootschap<http://www.ns.nl/emaildisclaimer> > > > Intern >
