You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Konstantine Karantasis (Jira)" <ji...@apache.org> on 2020/02/14 01:23:00 UTC

[jira] [Resolved] (KAFKA-5866) Let source/sink task to finish their job before exit

     [ https://issues.apache.org/jira/browse/KAFKA-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantine Karantasis resolved KAFKA-5866.
-------------------------------------------
    Resolution: Won't Do

I'm closing this ticket, as this is a quite old request and there's not a strong case for it. In contrast, it seems better in many ways to keep not allowing more records to be produced after a source task receives a stop signal. 

> Let source/sink task to finish their job before exit
> ----------------------------------------------------
>
>                 Key: KAFKA-5866
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5866
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 0.10.2.0
>            Reporter: Oleg Kuznetsov
>            Priority: Major
>
> My case is about reading files. When task stops to rebalance or for other reason, I want let it to read file till the end at least.
> I found that flag 
> {code:java}
> WorkerTask#stopping
> {code}
>  is set to true and only then 
> {code:java}
> SourceTask.stop()
> {code}
>  is called. This stopping flag prevents WorkerSourceTask from further ingestion (exit from 
> {code:java}
> while ( !isStopped()))
> {code}.
> Is it possible to let task to decide to work some more time and possibly produce more records from the moment of stop() was called on rebalance?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)