[jira] [Comment Edited] (FLINK-5048) Kafka Consumer (0.9/0.10) threading model leads problematic cancellation behavior

["Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927427#comment-15927427 ] 

Tzu-Li (Gordon) Tai edited comment on FLINK-5048 at 3/16/17 3:43 AM:
---------------------------------------------------------------------

Agreed, let's mark this issue as resolved and remove {{1.1.5}} from the fix versions then.


was (Author: tzulitai):
Agreed, let's resolve this issue and remove {{1.1.5}} from the fix versions then.

> Kafka Consumer (0.9/0.10) threading model leads problematic cancellation behavior
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-5048
>                 URL: https://issues.apache.org/jira/browse/FLINK-5048
>             Project: Flink
>          Issue Type: Bug
>          Components: Kafka Connector
>    Affects Versions: 1.1.3
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>            Priority: Blocker
>             Fix For: 1.2.0, 1.1.5
>
>
> The {{FLinkKafkaConsumer}} (0.9 / 0.10) spawns a separate thread that operates the KafkaConsumer. That thread is shielded from interrupts, because the Kafka Consumer has not been handling thread interrupts well.
> Since that thread is also the thread that emits records, it may block in the network stack (backpressure) or in chained operators. The later case leads to situations where cancellations get very slow unless that thread would be interrupted (which it cannot be).
> I propose to change the thread model as follows:
>   - A spawned consumer thread pull from the KafkaConsumer and pushes its pulled batch of records into a blocking queue (size one)
>   - The main thread of the task will pull the record batches from the blocking queue and emit the records.
> This allows actually for some additional I/O overlay while limiting the additional memory consumption - only two batches are ever held, one being fetched and one being emitted.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)