我们观察到,尽管我们的 kafka 生产率很高,但我们的 Apache Camel Kafka 只能处理 100Kb/秒。我们有 6 个 kafka 分区和 6 个 Apache Camel Kafka 消费者实例。
我们尝试了多线程选项 - threads(300, 500) 。但是我们看不到任何改进
如果有人能帮助理解正确的配置以提高kafka的消费率,那将是非常有帮助的。
我们正在使用 Apache Camel Kafka 消费者的所有默认设置。
我可以在 spring boot 应用程序启动时看到下面的 kafka 配置:
INFO 1 — [ main] o.a.k.clients.producer.ProducerConfig : ProducerConfig values:
acks = 1
batch.size = 16384
bootstrap.servers = [kafka1.xxx.net:9093, kafka2.xxx.net:9093, kafka3.xxx.net:9093, kafka4.xxx.net:9093, kafka5.xxx.net:9093, kafka6.xxx.net:9093]
buffer.memory = 33554432
client.dns.lookup = use_all_dns_ips
client.id = producer-1
compression.type = none
connections.max.idle.ms = 540000
delivery.timeout.ms = 120000
enable.idempotence = false
interceptor.classes = []
key.serializer = class org.apache.kafka.common.serialization.StringSerializer
linger.ms = 0
max.block.ms = 60000
max.in.flight.requests.per.connection = 5
max.request.size = 104857600
metadata.max.age.ms = 300000
metadata.max.idle.ms = 300000
metric.reporters = [org.apache.kafka.common.metrics.JmxReporter]
metrics.num.samples = 2
metrics.recording.level = INFO
metrics.sample.window.ms = 30000
partitioner.class = class org.apache.kafka.clients.producer.internals.DefaultPartitioner
receive.buffer.bytes = 65536000
reconnect.backoff.max.ms = 1000
reconnect.backoff.ms = 50
request.timeout.ms = 30000
retries = 0
retry.backoff.ms = 100
sasl.client.callback.handler.class = null
sasl.jaas.config = null
sasl.kerberos.kinit.cmd = /usr/bin/kinit
sasl.kerberos.min.time.before.relogin = 60000
sasl.kerberos.service.name = null
sasl.kerberos.ticket.renew.jitter = 0.05
sasl.kerberos.ticket.renew.window.factor = 0.8
sasl.login.callback.handler.class = null
sasl.login.class = null
sasl.login.refresh.buffer.seconds = 300
sasl.login.refresh.min.period.seconds = 60
sasl.login.refresh.window.factor = 0.8
sasl.login.refresh.window.jitter = 0.05
sasl.mechanism = GSSAPI
security.protocol = SSL
security.providers = null
send.buffer.bytes = 131072
socket.connection.setup.timeout.max.ms = 30000
socket.connection.setup.timeout.ms = 10000
ssl.cipher.suites = null
ssl.enabled.protocols = [TLSv1.2, TLSv1.3]
ssl.endpoint.identification.algorithm = https
ssl.engine.factory.class = null
ssl.key.password = [hidden]
ssl.keymanager.algorithm = SunX509
ssl.keystore.certificate.chain = null
ssl.keystore.key = null
ssl.keystore.location = /tmp/certs/XXX.jks
ssl.keystore.password = [hidden]
ssl.keystore.type = JKS
ssl.protocol = TLSv1.3
ssl.provider = null
ssl.secure.random.implementation = null
ssl.trustmanager.algorithm = PKIX
ssl.truststore.certificates = null
ssl.truststore.location = /tmp/certsFolder/kafka.truststore.jks
ssl.truststore.password = [hidden]
ssl.truststore.type = JKS
transaction.timeout.ms = 60000
transactional.id = null
value.serializer = class org.apache.kafka.common.serialization.StringSerializer
我们尝试了多线程选项 - .threads(300, 500) 。但是我们看不到任何改进。
是不是跟kafka消费属性有关系?
spring-boot-starter-parent 版本 - 2.6.8 org.apache.camel.springboot 版本 - 3.14.1
Kafka Partition 1 – Producer and Consumer:Producer是一条常量线。但是 Apache 骆驼消费者的消费率有起有落
Kafka Partition 2 – Producer和Consumer:Producer是一条常量线。但是 Apache 骆驼消费者的消费率有起有落
Kafka Partition 3 – Producer和Consumer:Producer是一条常量线。但是 Apache 骆驼消费者的消费率有起有落
Kafka Partition 4 – Producer和Consumer:Producer是一条常量线。但是 Apache camel consumer 的消费率只有 30 B/s。
Kafka Partition 5 - Producer和Consumer:Producer是一条常量线。但是 Apache camel consumer 的消费率只有 30 B/s。
Kafka Partition 6 – Producer和Consumer:Producer是一条常量线。但是 Apache 骆驼消费者的消费率有起有落。