You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Otavio Rodolfo Piske (Jira)" <ji...@apache.org> on 2021/09/21 07:52:00 UTC
[jira] [Updated] (CAMEL-13215) camel-kafka -consumerCount vs
consumerStreams problem with pool size
[ https://issues.apache.org/jira/browse/CAMEL-13215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Otavio Rodolfo Piske updated CAMEL-13215:
-----------------------------------------
Fix Version/s: 3.12.0
> camel-kafka -consumerCount vs consumerStreams problem with pool size
> ---------------------------------------------------------------------
>
> Key: CAMEL-13215
> URL: https://issues.apache.org/jira/browse/CAMEL-13215
> Project: Camel
> Issue Type: Task
> Components: camel-kafka
> Affects Versions: 2.23.1
> Reporter: Pablo
> Assignee: Otavio Rodolfo Piske
> Priority: Minor
> Fix For: 3.12.0
>
>
> Hi guys,
> Currently we are configuring camel-kafka component, but we don't understand at all the consumer properties related to concurrency.
> According to the configuration:
> consumersCount: The number of consumers that connect to kafka server (default 1)
> consumerStreams: Number of concurrent consumers on the consumer (default 10)
> But... Having a look to the source code, the consumerStreams is the number of threads the executor is configured.
> And a task is submitted to the executor for each kafka consumer, which is the consumerCount.
> So... I don't see what you get if you configure different values in consumerCount and consumerStreams with the current implementation.
> Basically I expected that if define consumerCount=1 and consumerStreams=10, which is the default. I would get 10 threads consuming from that Kafka consumer. But I end up having a pool of 10 threads with only a worker which is a single thread consumer.
>
> Talking with Andrea Cosentino, seems that this maybe it's a problem in the documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)