[
https://issues.apache.org/jira/browse/IGNITE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-19102:
-----------------------------------
Description:
Now it can be affected by Kafka group management side-effects:
# Leaving a group after 'max.poll.timeout' exceeds, because
{{KafkaToIgniteMetadataUpdater}} polls data only on demand, not in continuous
manner.
# Delays during consumer group rebalancing.
# Metadata topic should have single partition. Multiple consumers from the same
group can not subscribe on the same partition.
*Important:* {{KafkaConsumer}} in {{KafkaToIgniteMetadataUpdater}} must be
assigned to all partitions.
was:
In order to read data with guaranteed order, metadata topic must have only one
partition. To achieve this we should:
* Write binary types and marshaller mappings only to a single partition in
{{IgniteToKafkaCdcStreamer#onMappings}} and {{#onTypes}}.
* Print warnings into logs, when topic has more than one partition.
> CDC: Use manual assignment for consumer in KafkatoIgniteMetadtaUpdater
> ----------------------------------------------------------------------
>
> Key: IGNITE-19102
> URL: https://issues.apache.org/jira/browse/IGNITE-19102
> Project: Ignite
> Issue Type: Task
> Components: extensions
> Reporter: Ilya Shishkov
> Priority: Major
> Labels: IEP-59, ise
>
> Now it can be affected by Kafka group management side-effects:
> # Leaving a group after 'max.poll.timeout' exceeds, because
> {{KafkaToIgniteMetadataUpdater}} polls data only on demand, not in continuous
> manner.
> # Delays during consumer group rebalancing.
> # Metadata topic should have single partition. Multiple consumers from the
> same group can not subscribe on the same partition.
> *Important:* {{KafkaConsumer}} in {{KafkaToIgniteMetadataUpdater}} must be
> assigned to all partitions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
