ableegoldman commented on a change in pull request #10788:
URL: https://github.com/apache/kafka/pull/10788#discussion_r683057288
##########
File path:
streams/src/main/java/org/apache/kafka/streams/processor/internals/TaskManager.java
##########
@@ -1193,6 +1189,18 @@ public void updateTaskEndMetadata(final TopicPartition
topicPartition, final Lon
}
}
+ /**
+ * Checks for added or removed NamedTopologies that correspond to any
assigned tasks, and creates/freezes them if so
+ */
+ void handleTopologyUpdates() {
+ tasks.maybeCreateTasksFromNewTopologies();
+ for (final Task task : activeTaskIterable()) {
+ if
(topologyMetadata.namedTopologiesView().contains(task.id().namedTopology())) {
+ task.freezeProcessing();
Review comment:
This is another stupid bug...it should be freezing them if they _don't _
appear in the current topology. Tasks from removed named topologies are frozen
to prevent them from processing any more records, so yes, it is meant to be
permanent.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
