春季云流kafka commitfailedexception

发布于 2025-02-11 07:39:14 字数 3653 浏览 2 评论 0原文

我使用了spring-cloud-starter-stream-kafka 3.0.4.Release,我有以下错误:

org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing max.poll.interval.ms or by reducing the maximum size of batches returned in poll() with max.poll.records.
        at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator$OffsetCommitResponseHandler.handle(ConsumerCoordinator.java:900)
        at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator$OffsetCommitResponseHandler.handle(ConsumerCoordinator.java:840)
        at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:978)
        at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:958)
        at org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:204)
        at org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:167)
        at org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:127)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:578)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:388)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:294)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.pollNoWakeup(ConsumerNetworkClient.java:303)
        at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$HeartbeatThread.run(AbstractCoordinator.java:1104)

配置:

spring:
   cloud: 
     stream:  
       bindings:
         default:
           content-type: application/*+avro
         inputAddAccount:
           destination: dev_account
           group: dev_group
         ouputUpdateFile:
           destination: dev_update_file
           group: dev_group
           producer:
            useNativeEncoding: true
       kafka:
         binder:
           brokers: kafka1-dev:6667
           auto-create-topics: false
           consumer-properties:
             auto.offset.reset: latest
             auto.commit.interval.ms: 1000
             specific.avro.reader: true
             key.deserializer: org.apache.kafka.common.serialization.StringDeserializer
             value.deserializer: io.confluent.kafka.serializers.KafkaAvroDeserializer
             schema.registry.url: https://schema-registry1.dev:8088
             basic.auth.credentials.source: USER_INFO
             basic.auth.user.info: reader:reader
           producer-properties:
             acks: -1
             retries: 2147483647
             max.in.flight.requests.per.connection : 1
             request.timeout.ms: 10000
             key.serializer: org.apache.kafka.common.serialization.StringSerializer
             value.serializer: io.confluent.kafka.serializers.KafkaAvroSerializer
             schema.registry.url: https://schema-registry1.dev:8088
             basic.auth.credentials.source: USER_INFO
             basic.auth.user.info: reader:reader

I used spring-cloud-starter-stream-kafka 3.0.4.RELEASE, i have the below error:

org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing max.poll.interval.ms or by reducing the maximum size of batches returned in poll() with max.poll.records.
        at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator$OffsetCommitResponseHandler.handle(ConsumerCoordinator.java:900)
        at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator$OffsetCommitResponseHandler.handle(ConsumerCoordinator.java:840)
        at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:978)
        at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:958)
        at org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:204)
        at org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:167)
        at org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:127)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:578)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:388)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:294)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.pollNoWakeup(ConsumerNetworkClient.java:303)
        at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$HeartbeatThread.run(AbstractCoordinator.java:1104)

Configuration:

spring:
   cloud: 
     stream:  
       bindings:
         default:
           content-type: application/*+avro
         inputAddAccount:
           destination: dev_account
           group: dev_group
         ouputUpdateFile:
           destination: dev_update_file
           group: dev_group
           producer:
            useNativeEncoding: true
       kafka:
         binder:
           brokers: kafka1-dev:6667
           auto-create-topics: false
           consumer-properties:
             auto.offset.reset: latest
             auto.commit.interval.ms: 1000
             specific.avro.reader: true
             key.deserializer: org.apache.kafka.common.serialization.StringDeserializer
             value.deserializer: io.confluent.kafka.serializers.KafkaAvroDeserializer
             schema.registry.url: https://schema-registry1.dev:8088
             basic.auth.credentials.source: USER_INFO
             basic.auth.user.info: reader:reader
           producer-properties:
             acks: -1
             retries: 2147483647
             max.in.flight.requests.per.connection : 1
             request.timeout.ms: 10000
             key.serializer: org.apache.kafka.common.serialization.StringSerializer
             value.serializer: io.confluent.kafka.serializers.KafkaAvroSerializer
             schema.registry.url: https://schema-registry1.dev:8088
             basic.auth.credentials.source: USER_INFO
             basic.auth.user.info: reader:reader

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

缱倦旧时光 2025-02-18 07:39:14

org.apache.kafka.clients.consumer.commitfailedexception:COMM无法完成,因为该组已经重新平衡并将分区分配给另一个成员。这意味着随后对Poll()的后续调用之间的时间比配置的Max.poll.interval.ms更长,这通常意味着民意调查循环花费过多的时间消息处理。您可以通过增加max.poll.interval.ms或减小poll()中返回的最大批次()使用max.poll.records。来解决此

问题 。一条消息,而不是session.timeout.ms或max.poll.interval.ms。另外,查看您的配置,我没有看到这些属性,这意味着您的消费者正在使用默认值。请检查这些值,如果它小于处理记录的AVG时间,请用更长的值覆盖它们。

org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing max.poll.interval.ms or by reducing the maximum size of batches returned in poll() with max.poll.records.

They above exception occurs when your consumer takes longer time to process a message than session.timeout.ms or max.poll.interval.ms. Also, looking at your configuration, I am not seeing these properties, that means your consumer is using default values. Kindly check those values and if it is less than the avg time of processing a record, kindly overwrite them with a longer values.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文