[jira] [Updated] (KAFKA-10500) Add API to Start and Stop Stream Threads
[ https://issues.apache.org/jira/browse/KAFKA-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-10500: Description: Currently, there is no possibility in Kafka Streams to increase or decrease the number of stream threads after the Kafka Streams client has been started. Uncaught exceptions thrown in a stream thread kill the stream thread leaving the Kafka Streams client with less stream threads for processing than when the client was started. The only way to replace the killed stream thread is to restart the whole Kafka Streams client. For transient errors, it might make sense to replace a killed stream thread with a new one while users try to find the root cause of the error. That could be accomplished by starting a new stream thread in the uncaught exception handler of the killed stream thread. Part of KIP-663 [https://cwiki.apache.org/confluence/display/KAFKA/KIP-663%3A+API+to+Start+and+Shut+Down+Stream+Threads] was:Currently, there is no possibility in Kafka Streams to increase or decrease the number of stream threads after the Kafka Streams client has been started. Uncaught exceptions thrown in a stream thread kill the stream thread leaving the Kafka Streams client with less stream threads for processing than when the client was started. The only way to replace the killed stream thread is to restart the whole Kafka Streams client. For transient errors, it might make sense to replace a killed stream thread with a new one while users try to find the root cause of the error. That could be accomplished by starting a new stream thread in the uncaught exception handler of the killed stream thread. > Add API to Start and Stop Stream Threads > > > Key: KAFKA-10500 > URL: https://issues.apache.org/jira/browse/KAFKA-10500 > Project: Kafka > Issue Type: New Feature > Components: streams >Reporter: Bruno Cadonna >Assignee: Walker Carlson >Priority: Major > Labels: kip > > Currently, there is no possibility in Kafka Streams to increase or decrease > the number of stream threads after the Kafka Streams client has been started. > Uncaught exceptions thrown in a stream thread kill the stream thread leaving > the Kafka Streams client with less stream threads for processing than when > the client was started. The only way to replace the killed stream thread is > to restart the whole Kafka Streams client. For transient errors, it might > make sense to replace a killed stream thread with a new one while users try > to find the root cause of the error. That could be accomplished by starting a > new stream thread in the uncaught exception handler of the killed stream > thread. > Part of KIP-663 > [https://cwiki.apache.org/confluence/display/KAFKA/KIP-663%3A+API+to+Start+and+Shut+Down+Stream+Threads] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10500) Add API to Start and Stop Stream Threads
[ https://issues.apache.org/jira/browse/KAFKA-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-10500: Labels: kip (was: needs-kip) > Add API to Start and Stop Stream Threads > > > Key: KAFKA-10500 > URL: https://issues.apache.org/jira/browse/KAFKA-10500 > Project: Kafka > Issue Type: New Feature > Components: streams >Reporter: Bruno Cadonna >Assignee: Walker Carlson >Priority: Major > Labels: kip > > Currently, there is no possibility in Kafka Streams to increase or decrease > the number of stream threads after the Kafka Streams client has been started. > Uncaught exceptions thrown in a stream thread kill the stream thread leaving > the Kafka Streams client with less stream threads for processing than when > the client was started. The only way to replace the killed stream thread is > to restart the whole Kafka Streams client. For transient errors, it might > make sense to replace a killed stream thread with a new one while users try > to find the root cause of the error. That could be accomplished by starting a > new stream thread in the uncaught exception handler of the killed stream > thread. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10500) Add API to Start and Stop Stream Threads
[ https://issues.apache.org/jira/browse/KAFKA-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-10500: -- Parent: (was: KAFKA-10015) Issue Type: New Feature (was: Sub-task) > Add API to Start and Stop Stream Threads > > > Key: KAFKA-10500 > URL: https://issues.apache.org/jira/browse/KAFKA-10500 > Project: Kafka > Issue Type: New Feature > Components: streams >Reporter: Bruno Cadonna >Priority: Major > Labels: needs-kip > > Currently, there is no possibility in Kafka Streams to increase or decrease > the number of stream threads after the Kafka Streams client has been started. > Uncaught exceptions thrown in a stream thread kill the stream thread leaving > the Kafka Streams client with less stream threads for processing than when > the client was started. The only way to replace the killed stream thread is > to restart the whole Kafka Streams client. For transient errors, it might > make sense to replace a killed stream thread with a new one while users try > to find the root cause of the error. That could be accomplished by starting a > new stream thread in the uncaught exception handler of the killed stream > thread. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10500) Add API to Start and Stop Stream Threads
[ https://issues.apache.org/jira/browse/KAFKA-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-10500: -- Labels: needs-kip (was: ) > Add API to Start and Stop Stream Threads > > > Key: KAFKA-10500 > URL: https://issues.apache.org/jira/browse/KAFKA-10500 > Project: Kafka > Issue Type: Sub-task > Components: streams >Reporter: Bruno Cadonna >Priority: Major > Labels: needs-kip > > Currently, there is no possibility in Kafka Streams to increase or decrease > the number of stream threads after the Kafka Streams client has been started. > Uncaught exceptions thrown in a stream thread kill the stream thread leaving > the Kafka Streams client with less stream threads for processing than when > the client was started. The only way to replace the killed stream thread is > to restart the whole Kafka Streams client. For transient errors, it might > make sense to replace a killed stream thread with a new one while users try > to find the root cause of the error. That could be accomplished by starting a > new stream thread in the uncaught exception handler of the killed stream > thread. -- This message was sent by Atlassian Jira (v8.3.4#803005)
