You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2020/07/28 03:58:00 UTC
[jira] [Assigned] (KAFKA-10317) Global thread should honor shutdown
signal during bootstrapping
[ https://issues.apache.org/jira/browse/KAFKA-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias J. Sax reassigned KAFKA-10317:
---------------------------------------
Assignee: Matthias J. Sax
> Global thread should honor shutdown signal during bootstrapping
> ---------------------------------------------------------------
>
> Key: KAFKA-10317
> URL: https://issues.apache.org/jira/browse/KAFKA-10317
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Priority: Major
>
> During startup, the global thread will bootstrap all global stores before it enters its main store-update-loop. The store-update-loop exits, when `KafkaStreams#close()` is called.
> However, during the bootstrap phase there is no check if `KafkaStreams#close()` was called. And thus, KafkaStreams cannot be stopped during bootstrapping (ie, the bootstrapping cannot be interrupted).
> To make Kafka Streams more responsive, we should check if `close()` was called during bootstrapping, too.
> Note, that `KafkaStreams#start()` actually blocks during bootstrapping atm (cf KAFKA-7380) and thus we should fix both issue at once if possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)