You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "satishd (via GitHub)" <gi...@apache.org> on 2023/07/18 09:03:56 UTC
[GitHub] [kafka] satishd commented on a diff in pull request #14012: KAFKA-15181: fix(storage): wait for consumer to be synced after assigning partitions
satishd commented on code in PR #14012:
URL: https://github.com/apache/kafka/pull/14012#discussion_r1266471753
##########
storage/src/main/java/org/apache/kafka/server/log/remote/metadata/storage/ConsumerManager.java:
##########
@@ -139,6 +163,35 @@ public void close() throws IOException {
public void addAssignmentsForPartitions(Set<TopicIdPartition> partitions) {
consumerTask.addAssignmentsForPartitions(partitions);
+ waitTillMetaPartitionConsumptionCatchesUp();
Review Comment:
The latching mechanism as mentioned by @kamalcph is what we are currently using internally. @abhijeetk88 is planning to pull those changes to trunk and raise PR this week to handle the scenario.
--
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-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org