[
https://issues.apache.org/jira/browse/KAFKA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Yu updated KAFKA-7118:
------------------------------
Description: It was discovered that there is a performance constraint
relating to {{KafkaConsumer#close()}}. When several cores are modifying the
same consumer, a {{ConcurrentModification}} exception could result. This issue
was first posted on Spark. For testing details, see SPARK-23636 and
SPARK-19185. It would be preferable if multiple threads are allowed to modify
one {{KafkaConsumer}}. (was: It was discovered that there is a performance
constraint relating to {{KafkaConsumer#close()}}. When several cores are
modifying the same consumer, a {{ConcurrentModification}} exception could
result. This issue was first posted on Spark. For testing details, see
SPARK-23636. It would be preferable if multiple threads are allowed to modify
one {{KafkaConsumer}}.)
> Make KafkaConsumer compatible with multiple threads
> ---------------------------------------------------
>
> Key: KAFKA-7118
> URL: https://issues.apache.org/jira/browse/KAFKA-7118
> Project: Kafka
> Issue Type: Improvement
> Components: consumer
> Reporter: Richard Yu
> Priority: Major
> Labels: client, java, kip, needs-kip
>
> It was discovered that there is a performance constraint relating to
> {{KafkaConsumer#close()}}. When several cores are modifying the same
> consumer, a {{ConcurrentModification}} exception could result. This issue was
> first posted on Spark. For testing details, see SPARK-23636 and SPARK-19185.
> It would be preferable if multiple threads are allowed to modify one
> {{KafkaConsumer}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
