Change how --no-acking works #4
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add -S --ssl flag to use SSL (amqps)
no-ack should not mean be about auto-ack but rahter if we ack a message at all. This way we can actually get 1 message. Otherwise with auto-acking, we get more messages even with prefetch = 1; as the server will just push them to us. With --no-ack specified, we would not even pop 1 message from the server, it will always reque
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
I wanted to use
amqp consume -n 1to just get one message and exit.But I couldn't:
The auto-acking option set in amqp channel consume call would mean, that if there were more messages waiting, we would still get more then one message (even with prefetch =1).
I tried with --no-ack but then the actions would not be removed from the queue at all (because server would not receive any acks).
I changed the way --no-ack works - we always do auto-ack = false, and then we ack or not depending on the --no-ack flag.
Please check if this works also for your use case.