-
Notifications
You must be signed in to change notification settings - Fork 30
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
Bottleneck in publishing on a tight while loop #30
Comments
Re-created. Remember to change scripts broker connection details on both scripts. |
Thread with issue
All threads
|
Retrying with latest librdkafka... |
Tried with latest Kafka release - no difference Ref: current redhat 7 version Newest release .kfk.Version |
Ref: https://github.com/edenhill/librdkafka/blob/master/examples/producer.c |
Temp removing |
Think I can see the potential root of the problem now. In this occasion, thread is consuming all of the thread operations (main kdb thread). The poll is letting Kafka events happen. When Kafka events happen, they try to inform kdb to do stuff via a file descriptor (this happens every time the queue gets emptied). Queue is not able to be consumed by KDB for housekeeping & react to data to be read cos its spending 100% of its time publishing. I expect if the above example was changed to do a certain amount on a timer/etc each time it'd cause it not to hang (though this isn't the desired action the user wants to do). Will work on a change. |
To check whether return code error from pub is appropriate. Code can present queue full/etc were user could take action. |
linked to confluentinc/librdkafka#2932 |
Internally raised issue
Describe the bug
To Reproduce
consumer script
producer script
Expected behavior
Producer should not block in this scenario.
Screenshots
No applicable screenshots to explain this scenario further
Desktop (please complete the following information):
Behaviour has been seen in a variety of Linux environments and on MacOS so should be reproducible across multiple environments
Additional context
No applicable additional context
The text was updated successfully, but these errors were encountered: