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.

Sign up for GitHub

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

Jump to bottom

Message timeout scans #21

Closed
liljenback opened this issue Sep 24, 2013 · 3 comments
Closed

Message timeout scans #21

liljenback opened this issue Sep 24, 2013 · 3 comments
Assignees
@edenhill

Comments

@liljenback
Copy link

The unlikely condidtion for last_timeout_scan in rd_kafka_broker_serve that has * 1000000 will 'unlikely' trigger timeout scans, is this as intended, or should it be + 1000000 (1 second) to trigger scans a bit more frequent?
@ghost ghost assigned edenhill Sep 24, 2013
@edenhill
Copy link
Contributor

Good catch!

@edenhill
Copy link
Contributor

A fix for this (and UA partition message timeouts) will be available before the end of this week, along with more goodies.

edenhill added a commit that referenced this issue Oct 3, 2013
@edenhill
Proper timeouts for produced messages (issue #21)
887f5c3 
Timeout msgs regardless of partition (real or UA).
Added testcase for message timeouts.
@edenhill
Copy link
Contributor

edenhill commented Oct 3, 2013

This issue should now be fixed in the master branch.
Would be awesome if you could verify on your end and close the issue.

Thanks

@xiaojun789 xiaojun789 mentioned this issue Nov 8, 2013
Closed
@DEvil0000 DEvil0000 mentioned this issue Oct 12, 2015
Closed
@mlala-pan mlala-pan mentioned this issue Aug 5, 2016
Closed
@benli123 benli123 mentioned this issue Mar 17, 2017
Closed
9 tasks
@matthrae matthrae mentioned this issue Nov 8, 2018
Closed
@MockingJayWong MockingJayWong mentioned this issue Jul 9, 2019
Closed
7 tasks
@hyhtemple hyhtemple mentioned this issue Jun 30, 2020
Closed
Closed
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@edenhill edenhill

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edenhill @liljenback