Nikita Amelchev created IGNITE-20954:
----------------------------------------
Summary: [Extensions] cdc-ext: prohibit the same group for event
and metadata consumers
Key: IGNITE-20954
URL: https://issues.apache.org/jira/browse/IGNITE-20954
Project: Ignite
Issue Type: Task
Reporter: Nikita Amelchev
Assignee: Nikita Amelchev
The Kafka commit operation throws the exception if consumer group mixes manual
and subscription partition assignment (even for different topics). Expected
behavior not described: [Kafka Partition
Assignment|https://kafka.apache.org/28/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html#manualassignment].
{noformat}
[async-runnable-runner-1] ERROR
org.apache.kafka.clients.consumer.internals.ConsumerCoordinator - [Consumer
clientId=consumer-my-group-1, groupId=my-group] Offset commit failed on
partition my-topic-0 at offset 0: The coordinator is not aware of this member.
[async-runnable-runner-1] INFO
org.apache.kafka.clients.consumer.internals.ConsumerCoordinator - [Consumer
clientId=consumer-my-group-1, groupId=my-group] OffsetCommit failed with
Generation{generationId=-1, memberId='', protocol='null'}: The coordinator is
not aware of this member.
org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be
completed since the group has already rebalanced and assigned the partitions to
another member. This means that the time between subsequent calls to poll() was
longer than the configured max.poll.interval.ms, which typically implies that
the poll loop is spending too much time message processing. You can address
this either by increasing max.poll.interval.ms or by reducing the maximum size
of batches returned in poll() with max.poll.records.
{noformat}
Add the consumer group to reproduce:
{noformat}
CdcKafkaReplicationTest#kafkaToIgnite
KafkaToIgniteCdcStreamerConfiguration cfg = new
KafkaToIgniteCdcStreamerConfiguration();
cfg.setMetadataConsumerGroup("kafka-to-ignite-applier");
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
