为什么 kafka 消费者数百次消费相同的消息? [英] Why is the kafka consumer consuming the same message hundreds of times?

问题描述

我从日志中看到，665 次消耗了完全相同的消息.为什么会发生这种情况?

I see from the logs that exact same message is consumed by the 665 times. Why does this happen?

我也在日志中看到了这一点

I also see this in the logs

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 session.timeout.ms, which typically implies 
that the poll loop is spending too much time message processing. You can address this either by increasing the session 
timeout or by reducing the maximum size of batches returned in poll() with max.poll.records.

消费者属性

group.id=someGroupId
bootstrap.servers=kafka:9092
enable.auto.commit=false
key.deserializer=org.apache.kafka.common.serialization.StringDeserializer
value.deserializer=org.apache.kafka.common.serialization.StringDeserializer
session.timeout.ms=30000
max.poll.records=20

PS:是否可以从队列中的 1000 条消息中只使用特定数量的消息，例如 10、50 或 100 条消息?我正在查看fetch.max.bytes"配置，但它似乎是针对消息大小而不是消息数量.

PS: Is it possible to consume only a specific number of messages like 10 or 50 or 100 messages from the 1000 that are in the queue? I was looking at 'fetch.max.bytes' config, but it seems like it is for a message size rather than number of messages.

谢谢

推荐答案

答案在于对以下概念的理解:

The answer lies in the understanding of the following concepts:

• session.timeout.ms
• 心跳
• max.poll.interval.ms

在您的情况下，您的消费者通过 poll() 收到一条消息，但无法在 max.poll.interval.ms 时间内完成处理.因此，假设被 Broker 挂起，并且由于该消费者失去了所有分区的所有权而发生了分区的重新平衡.它被标记为死亡，不再是消费者组的一部分.

In your case, your consumer receives a message via poll() but is not able to complete the processing in max.poll.interval.ms time. Therefore, it is assumed hung by the Broker and re-balancing of partitions happen due to which this consumer loses the ownership of all partitions. It is marked dead and is no longer part of a consumer group.

然后，当您的消费者完成处理并再次调用 poll() 时，会发生两件事:

Then when your consumer completes the processing and calls poll() again two things happen:

1. 提交失败，因为消费者不再拥有分区.
2. Broker 识别出消费者再次启动，因此触发重新平衡，消费者再次加入消费者组，开始拥有分区并从 Broker 请求消息.由于较早的消息未标记为已提交(请参阅上面的 #1，提交失败)并且正在等待处理，因此代理再次将相同的消息传递给消费者.

消费者再次花费大量时间进行处理，并且由于无法在小于 max.poll.interval.ms 的时间内完成处理，因此 1. 和 2. 继续循环重复.

Consumer again takes a lot of time to process and since is unable to finish processing in less than max.poll.interval.ms, 1. and 2. keep repeating in a loop.

要解决此问题，您可以根据消费者需要多长时间进行处理，将 max.poll.interval.ms 增加到足够大的值.这样你的消费者就不会被标记为死亡，也不会收到重复的消息.但是，真正的解决方法是检查您的处理逻辑并尝试减少处理时间.

To fix the problem, you can increase the max.poll.interval.ms to a large enough value based on how much time your consumer needs for processing. Then your consumer will not get marked as dead and will not receive duplicate messages. However, the real fix is to check your processing logic and try to reduce the processing time.

这篇关于为什么 kafka 消费者数百次消费相同的消息?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！