[
https://issues.apache.org/jira/browse/KAFKA-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yasuhiro Matsuda updated KAFKA-3262:
------------------------------------
Description:
Current KafkaStreams polls records in the same thread as the data processing
thread. This makes debugging user code, as well as KafkaStreams itself,
difficult. When the thread is suspended by the debugger, the next heartbeat of
the consumer tie to the thread won't be send until the thread is resumed. This
often results in missed heartbeats and causes a group rebalance. So it may will
be a completely different context then the thread hits the break point the next
time.
We should consider using separate threads for polling and processing.
> Make KafkaStreams debugging friendly
> ------------------------------------
>
> Key: KAFKA-3262
> URL: https://issues.apache.org/jira/browse/KAFKA-3262
> Project: Kafka
> Issue Type: Sub-task
> Components: kafka streams
> Affects Versions: 0.9.1.0
> Reporter: Yasuhiro Matsuda
>
> Current KafkaStreams polls records in the same thread as the data processing
> thread. This makes debugging user code, as well as KafkaStreams itself,
> difficult. When the thread is suspended by the debugger, the next heartbeat
> of the consumer tie to the thread won't be send until the thread is resumed.
> This often results in missed heartbeats and causes a group rebalance. So it
> may will be a completely different context then the thread hits the break
> point the next time.
> We should consider using separate threads for polling and processing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
