Page History

...

• The shutdown is communicated to the other Kafka Streams clients through the rebalance protocol.

• All Stream Threads across the entire application are shutdown and they transit to state DEAD

• All Global Threads across the entire application are shutdown

• All Kafka Streams clients, i.e., the entire Kafka Streams application, is shutdown.

• All Kafka Streams clients transit to state ERROR. 

• The State directory cleaner thread stop
• The RocksDB metrics recording thread will stop.

If the old handler is set and the new one is not the behavior will not change. Other wise the new handler will take precedence.

In order to communicate the shutdown request from one client to the others we propose to update the SubcriptionInfoData to include a short field which will encode an error code. The error will be propagated through the metadata during a rejoin event via the assignor. The actual shutdown will be handled by the StreamsRebalnceListener, this is where the INCOMPLETE_SOURCE_TOPIC_METADATA error can also be handled.

...