Kafka 1.1.0 不断获得分区领导时代 [英] Kafka 1.1.0 keeps getting partition leader epoch

查看:25
本文介绍了Kafka 1.1.0 不断获得分区领导时代的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在使用 Kafka 时遇到问题.

I have a problem with Kafka.

我从 0.11.0.1 升级到 kafka 版本到 1.1.0.升级后,我收到太多以下警告消息.

I upgraded to kafka version from 0.11.0.1 to 1.1.0. After the upgrade, I'm getting the below warn message too much.

[2018-06-19 13:34:45,377] WARN Received a PartitionLeaderEpoch assignment for an epoch < latestEpoch. This implies messages have arrived out of order. New: {epoch:0, offset:350280659}, Current: {epoch:4, offset:126401625} for Partition: __consumer_offsets-48 (kafka.server.epoch.LeaderEpochFileCache)
[2018-06-19 13:34:45,386] WARN Received a PartitionLeaderEpoch assignment for an epoch < latestEpoch. This implies messages have arrived out of order. New: {epoch:0, offset:793868383}, Current: {epoch:4, offset:792201264} for Partition: __consumer_offsets-42 (kafka.server.epoch.LeaderEpochFileCache)
[2018-06-19 13:34:45,388] WARN Received a PartitionLeaderEpoch assignment for an epoch < latestEpoch. This implies messages have arrived out of order. New: {epoch:0, offset:793868384}, Current: {epoch:4, offset:792201264} for Partition: __consumer_offsets-42 (kafka.server.epoch.LeaderEpochFileCache)
[2018-06-19 13:34:45,400] WARN Received a PartitionLeaderEpoch assignment for an epoch < latestEpoch. This implies messages have arrived out of order. New: {epoch:0, offset:793868385}, Current: {epoch:4, offset:792201264} for Partition: __consumer_offsets-42 (kafka.server.epoch.LeaderEpochFileCache)

如何解决此警告消息?

推荐答案

我重新分配了发出此类警告消息的分区.我不再收到这些警告消息.如果您收到这些消息,您可以尝试重新分配分区.它对我有用.

I reassigned the partitions that issued this kind of warn message. I no longer receive these warn messages. If you are getting like these messages, you can try reassign partitions. It worked for me.

这篇关于Kafka 1.1.0 不断获得分区领导时代的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆