Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-evaluate pulse prefetch options #27

Open
marco-c opened this issue Nov 29, 2019 · 3 comments
Open

Re-evaluate pulse prefetch options #27

marco-c opened this issue Nov 29, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@marco-c
Copy link
Collaborator

marco-c commented Nov 29, 2019

There is a no_ack method for basic_consume. This way we could run pulse listener for the same queue on different machines without incurring in the problem of getting the same message on different machines.

@marco-c
Copy link
Collaborator Author

marco-c commented Nov 29, 2019

Reading a bit the documentation of RabbitMQ, it sounds like duplicated messages might not be possible.
From https://www.rabbitmq.com/confirms.html#automatic-requeueing:

When manual acknowledgements are used, any delivery (message) that was not acked is automatically requeued when the channel (or connection) on which the delivery happened is closed.

@La0
Copy link
Contributor

La0 commented Nov 29, 2019

Depends on #20

@marco-c marco-c changed the title Acknowledge and consume pulse messages at the same time Re-evaluate pulse prefetch options Dec 3, 2019
@marco-c
Copy link
Collaborator Author

marco-c commented Dec 3, 2019

We are currently using prefectCount of 1 and prefetcSize of 0, this could adversely affect performance.

@marco-c marco-c added the enhancement New feature or request label Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants