[ https://issues.apache.org/jira/browse/KAFKA-9540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sophie Blee-Goldman resolved KAFKA-9540. ---------------------------------------- Fix Version/s: 2.6.0 Resolution: Fixed > Application getting "Could not find the standby task 0_4 while closing it" > error > -------------------------------------------------------------------------------- > > Key: KAFKA-9540 > URL: https://issues.apache.org/jira/browse/KAFKA-9540 > Project: Kafka > Issue Type: Bug > Components: streams > Affects Versions: 2.4.0, 2.5.0 > Reporter: Badai Aqrandista > Priority: Minor > Fix For: 2.4.1, 2.6.0 > > > Because of this the following line, there is a possibility that some standby > tasks might not be created: > https://github.com/apache/kafka/blob/2.4.0/streams/src/main/java/org/apache/kafka/streams/processor/internals/StreamThread.java#L436 > Then causing this line to not adding the task to standby task list: > https://github.com/apache/kafka/blob/2.4.0/streams/src/main/java/org/apache/kafka/streams/processor/internals/StreamThread.java#L299 > But this line assumes that all standby tasks are to be created and add it to > the standby list: > https://github.com/apache/kafka/blob/2.4.0/streams/src/main/java/org/apache/kafka/streams/processor/internals/TaskManager.java#L168 > This results in user getting this error message on the next > PARTITION_ASSIGNMENT state: > {noformat} > Could not find the standby task 0_4 while closing it > (org.apache.kafka.streams.processor.internals.AssignedStandbyTasks:74) > {noformat} > But the harm caused by this issue is minimal: No standby task for some > partitions. And it is recreated on the next rebalance anyway. So, I suggest > lowering this message to WARN. Or probably check to WARN when standby task > could not be created. -- This message was sent by Atlassian Jira (v8.3.4#803005)