[ 
https://issues.apache.org/jira/browse/IGNITE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Shishkov updated IGNITE-19102:
-----------------------------------
    Description: 
Currently, {{KafkaToIgniteMetadataUpdater}} uses {{KafkaConsumer#subscribe}}, 
which lead to utilization of the consumer group management [1, "Consumer Groups 
and Topic Subscriptions"].  Kafka group management has some side-effects:
# {{KafkaConsumer}} leaves consumer group after {{max.poll.interval.ms}} 
exceeds [2], 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 
subscribed / assigned to all partitions.

Links:
# 
https://kafka.apache.org/27/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html
# 
https://kafka.apache.org/27/documentation.html#consumerconfigs_max.poll.interval.ms

  was:
Currently, {{KafkaToIgniteMetadataUpdater}} uses {{KafkaConsumer#subscribe}}, 
which lead to utilization of the consumer group management.  Kafka group 
management has some side-effects:
# {{KafkaConsumer}} leaves consumer group after {{max.poll.interval.ms}} 
exceeds [1], 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 
subscribed / assigned to all partitions.

Links:
# https://kafka.apache.org/documentation/#consumerconfigs_max.poll.interval.ms


> 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
>
> Currently, {{KafkaToIgniteMetadataUpdater}} uses {{KafkaConsumer#subscribe}}, 
> which lead to utilization of the consumer group management [1, "Consumer 
> Groups and Topic Subscriptions"].  Kafka group management has some 
> side-effects:
> # {{KafkaConsumer}} leaves consumer group after {{max.poll.interval.ms}} 
> exceeds [2], 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 
> subscribed / assigned to all partitions.
> Links:
> # 
> https://kafka.apache.org/27/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html
> # 
> https://kafka.apache.org/27/documentation.html#consumerconfigs_max.poll.interval.ms



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to