fix: always ack message #138
Closed
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
adamdecaf
reviewed
Sep 27, 2022
| @@ -186,6 +186,7 @@ func contains(err error, options ...string) bool { | |||
| } | |||
|
|
|||
| func (fr *FileReceiver) processMessage(msg *pubsub.Message) error { | |||
| msg.Ack() | |||
|
I've combined this into #140 |
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.
Changes
Always
ackmessage to move the consumer offset forward.Why Are Changes Being Made
Please validate my assumption If you must
ackthe message to move the consumer offset regardless of a failure, you can potentially queue the system forever when a loss is expected.The failures are being logged today, so it should be good from that end.
The final solution would be to move the message into A DLQ (Dead-Letter Queue) in the case of a failure.