chia7712 commented on PR #16922:
URL: https://github.com/apache/kafka/pull/16922#issuecomment-2466828413

   @nicktelford It seems this PR introduced some new behavior that breaks the 
E2E test `StreamsUpgradeTest#test_rolling_upgrade_with_2_bounces`. Could you 
please take a look at the following error and issue: 
[KAFKA-17978](https://issues.apache.org/jira/browse/KAFKA-17978)?
   
   ```
   [2024-11-10 17:47:44,001] ERROR stream-thread 
[StreamsUpgradeTest-4b4612d4-0d0f-41e2-8117-e1e9ba6a0d15-StreamThread-1] Failed 
to recycle task 1_0 cleanly. Attempting to close remaining tasks before 
re-throwing: (org.apache.kafka.streams.processor.internals.TaskManager)
   org.apache.kafka.streams.errors.TopologyException: Invalid topology: Topic 
StreamsUpgradeTest-KTABLE-FK-JOIN-SUBSCRIPTION-REGISTRATION-0000000011-topic is 
unknown to the topology. This may happen if different KafkaStreams instances of 
the same application execute different Topologies. Note that Topologies are 
only identical if all operators are added in the same order.
        at 
org.apache.kafka.streams.processor.internals.StreamTask$RecordQueueCreator.createQueue(StreamTask.java:1410)
        at 
org.apache.kafka.streams.processor.internals.StreamTask.createPartitionQueues(StreamTask.java:238)
        at 
org.apache.kafka.streams.processor.internals.StreamTask.<init>(StreamTask.java:214)
        at 
org.apache.kafka.streams.processor.internals.ActiveTaskCreator.createActiveTaskFromStandby(ActiveTaskCreator.java:206)
        at 
org.apache.kafka.streams.processor.internals.TaskManager.convertStandbyToActive(TaskManager.java:896)
        at 
org.apache.kafka.streams.processor.internals.TaskManager.recycleTaskFromStateUpdater(TaskManager.java:992)
        at 
org.apache.kafka.streams.processor.internals.TaskManager.handleStartupTaskReuse(TaskManager.java:568)
        at 
org.apache.kafka.streams.processor.internals.TaskManager.handleTasksWithStateUpdater(TaskManager.java:545)
        at 
org.apache.kafka.streams.processor.internals.TaskManager.handleAssignment(TaskManager.java:398)
        at 
org.apache.kafka.streams.processor.internals.StreamsPartitionAssignor.onAssignment(StreamsPartitionAssignor.java:1559)
        at 
org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.invokeOnAssignment(ConsumerCoordinator.java:327)
        at 
org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.onJoinComplete(ConsumerCoordinator.java:416)
        at 
org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:504)
        at 
org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:415)
        at 
org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:511)
        at 
org.apache.kafka.clients.consumer.internals.ClassicKafkaConsumer.updateAssignmentMetadataIfNeeded(ClassicKafkaConsumer.java:657)
        at 
org.apache.kafka.clients.consumer.internals.ClassicKafkaConsumer.poll(ClassicKafkaConsumer.java:621)
        at 
org.apache.kafka.clients.consumer.internals.ClassicKafkaConsumer.poll(ClassicKafkaConsumer.java:602)
        at 
org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:836)
        at 
org.apache.kafka.streams.processor.internals.StreamThread.pollRequests(StreamThread.java:1266)
        at 
org.apache.kafka.streams.processor.internals.StreamThread.pollPhase(StreamThread.java:1211)
        at 
org.apache.kafka.streams.processor.internals.StreamThread.runOnceWithoutProcessingThreads(StreamThread.java:944)
        at 
org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:711)
        at 
org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:671)
   ```


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to