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

Manually commiting in Rebus with Kafka #4

Closed
mookid8000 opened this issue Mar 25, 2020 · 2 comments
Closed

Manually commiting in Rebus with Kafka #4

mookid8000 opened this issue Mar 25, 2020 · 2 comments

Comments

@mookid8000
Copy link

Hi there, just want to direct your attention towards this question 👇

https://stackoverflow.com/questions/60834095/manually-commiting-in-rebus-with-kafka

🙂

@glazkovalex
Copy link
Owner

Hello, @mookid8000!
I answered that question: If you are not satisfied with the default option EnableAutoCommit = true, you can set its value, as well as all other parameters for the producer and consumer in the configuration parameters.
EnableAutoCommit = false,
How this is done is shown in this example of using transport "Rebus.Kafka": https://github.com/glazkovalex/Rebus.Kafka/blob/master/Examples/Scaleout.Producer/Program.cs

Notice that the current version of the transport with disabled autoCommit, receives five messages and after processing moves the pointer. In other words, if the service is interrupted with autoCommit disabled, the service can re-process up to five messages when restarting. The number of these re-processed messages can be changed in future versions of the transport "Rebus.Kafka".

@glazkovalex
Copy link
Owner

glazkovalex commented Jan 8, 2024

Rebus.Kafka version 3.0.1 now supports RetryStrategy - automatic retries and error handling. Confirmations of receipt of messages are now sent not after they are received, but only after successful processing of messages or sending them to the error topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants