Krutik Gadhiya
07/06/2023, 10:14 AMKafkaSource<Map<String, Object>> logSource = KafkaSource.<Map<String, Object>>builder()
.setBootstrapServers(BOOTSTRAP_SERVER)
.setTopics(SOURCE_TOPIC)
.setGroupId("group2")
.setStartingOffsets(OffsetsInitializer.latest())
.setValueOnlyDeserializer(new LogDeserializer())
.build();
also try to list groups using rpk group list, but that didn't show any groupssap1ens
07/06/2023, 4:17 PMcommit.offsets.on.checkpoint , should be set to true. Plus, checkpointing must be enabled.Krutik Gadhiya
07/06/2023, 4:19 PMsap1ens
07/06/2023, 4:20 PMenable.auto.commit, but it’s not recommended.Krutik Gadhiya
07/06/2023, 4:23 PM<http://auto.commit.interval.ms|auto.commit.interval.ms> and enable.auto.commit the redpanda ui shows the group but its status ia emptyKrutik Gadhiya
07/06/2023, 4:24 PMKrutik Gadhiya
07/07/2023, 7:30 AMcommit.offsets.on.checkpoint to true but after that the topic does not show any events.
KafkaSource<Map<String, Object>> logSource = KafkaSource.<Map<String, Object>>builder()
.setBootstrapServers("10.50.1.199:9092")
.setTopics("raw_logs")
.setProperty("group.id", "krutik1")
.setProperty("commit.offsets.on.checkpoint", "true")
.setStartingOffsets(OffsetsInitializer.latest())
.setValueOnlyDeserializer(new LogDeserializer())
.build();
now this does creates a group but the state of the group shows Empty
Note: there is a delay between the job start and group showing in Redpanda UI and also it is note consistent some times the group shows up after the job is canceled
And also if two consumer in the same group consuming from same topic each consumer should consume unique records, for e.g. if I send 10 events in topic X and the two consumer are in same group consuming from that topic then each should not receive same event, But that is not happening in this caseKrutik Gadhiya
07/11/2023, 6:11 AMAndré Midea Jasiskis
07/11/2023, 11:33 AM