-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
async producer not to circuit beak on partitioner errors #466
Comments
The reason the circuit breaker was added is the case of messages being produced to a topic that does not exists. This will fail very slowly, due to the fact that the error ( So the circuit breaker was added, but we didn't really think of other use cases. Maybe we can fix the above problem in a better way. |
@ssahukar this should be fixed in the latest master, if I understood you correctly |
Thanks Evan. I am following the discussion and it seems it would fix the issue I am Appreciate the quick turn around on this. On 9 June 2015 at 11:28, Evan Huus notifications@github.com wrote:
|
I have met a problem recently. My kafka has disabled automatic topic creation, once a lot of illegal I'm confusing that in which case |
If Partitioner.Partition() function returns an error, the circuit breaker breaks the circuit and drops some of the subsequent messages. I think Sarama should only drop the message for which partitioner returned an error and send that error to the application through the error channel.
In our application with a custom partitioner, we want to drop the messages that get produced with an invalid key, in which case the expected behavior is to drop only that message but to continue processing the other messages as usual, without a circuit break.
The text was updated successfully, but these errors were encountered: