qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ganesh Murthy <gmur...@redhat.com>
Subject Re: Dispatch Router prefetch
Date Fri, 08 Mar 2019 14:11:06 GMT
On Fri, Mar 8, 2019 at 7:59 AM HADI Ali <Ali.HADI@murex.com> wrote:

> Hello,
>
> We are actually using in our cluster multiple brokers and thus we need to
> define the same address on multiple brokers.
> For this, we cannot use linkroutes as suggested, but we still need to have
> the correct behavior of the TTL in our cluster.
>
> Is it an option to manage the TTL of the message at the level of the
> dispatch router since we have all of the information needed in the message
> headers?
>
At present the router does not deal with TTL. We would welcome a pull
request if you would like to have this feature in the router. Thanks.

> In Internet Protocol, ipv4 for example, the routers manage the TTL and
> discard any expired messages.
>
> Or make it feasible to have the autolinks propagate the credit directly
> from consumers? Therefore the dispatch router will only transit messages
> and the broker will handle the lifecycle of the message.
>
> Thank you,
> Ali
>
> -----Original Message-----
> From: Gordon Sim <gsim@redhat.com>
> Sent: mercredi 6 mars 2019 16:25
> To: users@qpid.apache.org
> Subject: Re: Dispatch Router prefetch
>
> On 06/03/2019 1:20 pm, ali hadi wrote:
> > We are using a cluster with one Dispatch Router version 1.5.0 and one
> > Broker-J version 7.1.0 on which we created a queue with a TTL of 5
> seconds .
> >
> >
> > We are noticing that the dispatch is prefetching messages from the
> > broker ( messages become in acquired state ) as soon as the consumer
> > establishes a connection with the dispatch and before starting
> > consuming. This is causing the messages to not be discarded after the
> > TTL expires and the consumer receiving the expired message.
> >
> >
> > We tried changing the linkCapacity on the level of the connector to 1
> > which allowed us to prefetch one message only instead of the default 250.
> >
> >
> > We are trying to find a way to remove completely the prefetch of the
> > dispatch in order to have the correct behavior from the TTL with our
> > cluster.
> >
> > Are there any flags or properties to be set in order for the dispatch
> > to only fetch a message on consumer demand?
>
> When using autolinks, the autolink for messages from the broker to the
> router will at present be activate as soon as there is an active receiver
> for the messages, whether or not that receiver has credit. In message
> routing the credit is not directly propagated from client to broker.
>
> If you use a link route then credit would be propagated directly, i.e.
> only when your client issues credit will the link between broker and
> router get credit (and it will be the exact same amount).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
> *******************************
> This e-mail contains information for the intended recipient only. It may
> contain proprietary material or confidential information. If you are not
> the intended recipient you are not authorized to distribute, copy or use
> this e-mail or any attachment to it. Murex cannot guarantee that it is
> virus free and accepts no responsibility for any loss or damage arising
> from its use. If you have received this e-mail in error please notify
> immediately the sender and delete the original email received, any
> attachments and all copies from your system.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message