[
https://issues.apache.org/jira/browse/KAFKA-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Seweryn Habdank-Wojewodzki updated KAFKA-5861:
----------------------------------------------
Description:
Recently implemented close( withTimeout ) for streams does not work under load
conditions in the multi-threaded KStream application.
Where there are more consuming threads and there many messages in stream, then
close ( withTimeout ) does not work.
1. Timeout is not respected at all and
2. application is hanging in some streaming chaos. Theoretically threads are
working - they are busy with themselves, so the app cannot end, but they are
not processing any further messages.
was:
Recently implemented stop( withTimeout ) for streams does not work under load
conditions in the multi-threaded KStream application.
Where there are more consuming threads and there many messages in stream, then
stop ( withTimeout ) does not work.
1. Timeout is not respected at all and
2. application is hanging in some streaming chaos. Theoretically threads are
working - they are busy with themselves, so the app cannot end, but they are
not processing any further messages.
> KStream close( withTimeout ) - does not work under load conditions in the
> multithreaded KStream application
> -----------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-5861
> URL: https://issues.apache.org/jira/browse/KAFKA-5861
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.11.0.0
> Reporter: Seweryn Habdank-Wojewodzki
>
> Recently implemented close( withTimeout ) for streams does not work under
> load conditions in the multi-threaded KStream application.
> Where there are more consuming threads and there many messages in stream,
> then close ( withTimeout ) does not work.
> 1. Timeout is not respected at all and
> 2. application is hanging in some streaming chaos. Theoretically threads are
> working - they are busy with themselves, so the app cannot end, but they are
> not processing any further messages.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
