KIP-62 / KAFKA-3888: Allow consumer to send heartbeats from a background thread
See original GitHub issueIssue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:27 (3 by maintainers)
Top Results From Across the Web
KIP-62: Allow consumer to send heartbeats from a background
When a rebalance begins, the background thread will continue sending heartbeats. The consumer will not rejoin the group until processing ...
Read more >What does the heartbeat thread do in Kafka Consumer?
Obviously the easiest solution is to send some status updates via network saying that we're still alive and evict each other based on...
Read more >Confluent Platform 3.1.1 Release Notes
... KAFKA-3888: Allow consumer to send heartbeats in background thread (KIP-62); KAFKA-3920: Add Schema source connector to Kafka Connect ...
Read more >Prevent kafka consumer from timing out for long process
Since Kafka 0.10.1, consumers do have a background thread for sending heartbeats: ...
Read more >Kafka Misc - Massive Technical Interviews Tips
https://issues.apache.org/jira/browse/KAFKA-3888. Allow consumer to send heartbeats in background thread (KIP-62)
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I would like to start working on this, we have multiple services at my day job that are impacted by this (and just realized there may be more due to #1039).
Unfortunately, I’ve never really worked with Java, so will be a bit slow trying to figure this out.
@tvoinarovskyi do you have any pointers on where to look in the Java code for where to start changing things compared to how they are in
kafka-python
today?Hey @jeffwidman Sorry, but GIL will not block you from doing IO in a separate thread. At least if you are not doing something crazy like passing all messages in a pure C code, that processes them. Python will yield GIL after some time (python3) or instruction count (python2), so as long as you are not stuck in C code it should be OK.