ableegoldman commented on a change in pull request #10788:
URL: https://github.com/apache/kafka/pull/10788#discussion_r682230209
##########
File path:
streams/src/main/java/org/apache/kafka/streams/processor/internals/ActiveTaskCreator.java
##########
@@ -64,6 +65,9 @@
private final Map<TaskId, StreamsProducer> taskProducers;
private final StreamThread.ProcessingMode processingMode;
+ // tasks may be assigned for a NamedTopology that is not yet known by this
host, and saved for later creation
+ private final Map<TaskId, Set<TopicPartition>> unknownTasksToBeCreated =
new HashMap<>();
Review comment:
I think we discussed this already, but in case anyone else is wondering:
the leader will always assign tasks based on its view of the current named
topologies and topics, ie it does not check on individual subscriptions since
the group is assumed to be eventually consistent in this regard. (Note this is
actually no different than today; even if each instance of an app has a
different input topic in their topology, they will all wind up receiving tasks
for whichever topic the leader happened to have.)
--
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
