Can we use quorum queue for RPC System

[Saineshwar Begari]

1. if we have 3 nodes then how it will behave. 

[Michal Kuratczyk]

In the RPC scenario, you usually want low and stable latency, while data safety is

not that important (a request from a few seconds ago might as well be dropped,

because the request was either already retried or timed out).

Therefore, classic queues v2 (obviously not mirrored) are probably the best option.

They will be the default in 3.13. In 3.12 use x-queue-version=2 when declaring the queue

or default to v2 in the config file:

classic_queue.default_version = 2

Quorum queues favour data safety and therefore have the overhead of replication

and fsync. They also perform some internal batching for higher throughput.

Therefore are not the best choice for low latency.

I'd highly recommend testing your workload though.

Best,

On Thu, Aug 24, 2023 at 9:19 AM 'Saineshwar Begari' via rabbitmq-users <rabbitm...@googlegroups.com> wrote:

1. if we have 3 nodes then how it will behave. 

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/e1a5978b-4588-4b9b-a791-705c4b75ba1fn%40googlegroups.com.

--

Michał

RabbitMQ team

[Saineshwar Begari]

Hi Michal,

Any other way to achieve RPC with durable queues and instant reply scenarios. 

Please guide me.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAA81d0t-SawCPYnShOKiEBFMC8pEUX3OP_6y1eRZNZNZh2Dtig%40mail.gmail.com.

[Michal Kuratczyk]

Please say what you don't like about my previous answer rather than requesting a different one. :)

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CADPG_NzLnoWfsh1b-axbs%3DUf%2BvTMszjX313JvR8hgW__DZ2p%2Bg%40mail.gmail.com.

--

Michał

RabbitMQ team

[Saineshwar Begari]

Data safety with RPC scenario. 

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAA81d0tEvhDVUw0KkR5VbiYpzazqe25_Uk5EqexDCwc0aSGrCA%40mail.gmail.com.

[Michal Kuratczyk]

Please put some effort into asking the questions if you expect further help from me.

Provide you actual requirements ("RPC" gives some idea, but our understanding of "RPC" can be very different).

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CADPG_NyNp6cQKCOUb9KzCdr0dXaVCmfEsUSQsc6unKrrXnCMmw%40mail.gmail.com.

--

Michał

RabbitMQ team

[Saineshwar Begari]

Send an email Scenario 

----------

Producer inserts a message in rabbit mq . This message will be read by Consumer and insta reply to that message should be received to the Producer.  

Reading email Scenario

----------

Producer inserts a message in rabbit mq . This message will be read by Consumer and insta reply to that message should be received to the Producer.  

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAA81d0sVGb5WHgM_tSp5cQHMO-31LNf440JQVKb8GqGErxGt0w%40mail.gmail.com.

[Michal Kuratczyk]

Ok, so in your case the latency is not that important I guess (because sending an email is relatively slow anyway),

but data safety is important (you want to make sure that the messages get delivered). So what's your concern

about using quorum queues?

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CADPG_NwOZrp7cv2YGNbnjvpZOnXHtf-U7WRrOSg_hNTOPwRBRw%40mail.gmail.com.

--

Michał

RabbitMQ team

[Saineshwar Begari]

Thank you Michal Kuratczyk to Reply to query got some new thoughts with your answers.

I got answer is we cannot use quorum queue with RPC.

It my last query.

if we are using RPC then how to avoid Message loss and what should follow for high efficiency. 

[Michal Kuratczyk]

"How to implement data-safe and performance distributed systems" is a question way beyond the scope of a mailing list. :)

A few obvious items in the context of RabbitMQ:

* use publisher confirms

* use consume acknowledgments

* keep the messages small

* test, test, test

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/ffca6188-b009-466b-a807-fa95454fcaa4n%40googlegroups.com.

--

Michał

RabbitMQ team