[KAFKA-5697] StreamThread.shutdown() need to interrupt the stream threads to break the loop

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: streams
• Labels: newbie
• Assignee: John Roesler
• Reporter: Guozhang Wang
• Created: 03/Aug/17 22:31
• Updated: 15/May/20 02:43
• Resolved: 08/Jun/18 17:55

Description

In StreamThread.shutdown() we currently do nothing but set the state, hoping the stream thread may eventually check it and shutdown itself. However, under certain scenarios the thread may get blocked within a single loop and hence will never check on this state enum. For example, it's consumer.poll call trigger ensureCoordinatorReady() which will block until the coordinator can be found. If the coordinator broker is never up and running then the Stream instance will be blocked forever.

A simple way to produce this issue is to start the work count demo without starting the ZK / Kafka broker, and then it will get stuck in a single loop and even `ctrl-C` will not stop it since its set state will never be read by the thread:

[2017-08-03 15:17:39,981] WARN Connection to node -1 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2017-08-03 15:17:40,046] WARN Connection to node -1 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2017-08-03 15:17:40,101] WARN Connection to node -1 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2017-08-03 15:17:40,206] WARN Connection to node -1 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2017-08-03 15:17:40,261] WARN Connection to node -1 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2017-08-03 15:17:40,366] WARN Connection to node -1 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2017-08-03 15:17:40,472] WARN Connection to node -1 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
^C[2017-08-03 15:17:40,580] WARN Connection to node -1 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)

 

Issue Links

• fixes: KAFKA-7004 Support configurable restore consumer poll timeout
• is blocked by: KAFKA-7000 KafkaConsumer.position should wait for assignment metadata
• is duplicated by: KAFKA-6783 consumer poll(timeout) blocked infinitely when no available bootstrap server
• links to: GitHub Pull Request #4855
• links to: GitHub Pull Request #4930
• links to: GitHub Pull Request #5035
• links to: GitHub Pull Request #5107
• mentioned in: Page Loading...