问题描述
我正在 3 个 EC2 实例上运行 Kafka 集群.每个实例运行 kafka (0.11.0.1) 和 zookeeper (3.4).我的主题配置为每个主题有 20 个分区，ReplicationFactor 为 3.
I'm running a Kafka cluster on 3 EC2 instances. Each instance runs kafka (0.11.0.1) and zookeeper (3.4). My topics are configured so that each has 20 partitions and ReplicationFactor of 3.
今天我注意到有些分区拒绝同步到所有三个节点.举个例子:
Today I noticed that some partitions refuse to sync to all three nodes. Here's an example:
bin/kafka-topics.sh --zookeeper "10.0.0.1:2181,10.0.0.2:2181,10.0.0.3:2181" --describe --topic prod-decline
Topic:prod-decline PartitionCount:20 ReplicationFactor:3 Configs:
Topic: prod-decline Partition: 0 Leader: 2 Replicas: 1,2,0 Isr: 2
Topic: prod-decline Partition: 1 Leader: 2 Replicas: 2,0,1 Isr: 2
Topic: prod-decline Partition: 2 Leader: 0 Replicas: 0,1,2 Isr: 2,0,1
Topic: prod-decline Partition: 3 Leader: 1 Replicas: 1,0,2 Isr: 2,0,1
Topic: prod-decline Partition: 4 Leader: 2 Replicas: 2,1,0 Isr: 2
Topic: prod-decline Partition: 5 Leader: 2 Replicas: 0,2,1 Isr: 2
Topic: prod-decline Partition: 6 Leader: 2 Replicas: 1,2,0 Isr: 2
Topic: prod-decline Partition: 7 Leader: 2 Replicas: 2,0,1 Isr: 2
Topic: prod-decline Partition: 8 Leader: 0 Replicas: 0,1,2 Isr: 2,0,1
Topic: prod-decline Partition: 9 Leader: 1 Replicas: 1,0,2 Isr: 2,0,1
Topic: prod-decline Partition: 10 Leader: 2 Replicas: 2,1,0 Isr: 2
Topic: prod-decline Partition: 11 Leader: 2 Replicas: 0,2,1 Isr: 2
Topic: prod-decline Partition: 12 Leader: 2 Replicas: 1,2,0 Isr: 2
Topic: prod-decline Partition: 13 Leader: 2 Replicas: 2,0,1 Isr: 2
Topic: prod-decline Partition: 14 Leader: 0 Replicas: 0,1,2 Isr: 2,0,1
Topic: prod-decline Partition: 15 Leader: 1 Replicas: 1,0,2 Isr: 2,0,1
Topic: prod-decline Partition: 16 Leader: 2 Replicas: 2,1,0 Isr: 2
Topic: prod-decline Partition: 17 Leader: 2 Replicas: 0,2,1 Isr: 2
Topic: prod-decline Partition: 18 Leader: 2 Replicas: 1,2,0 Isr: 2
Topic: prod-decline Partition: 19 Leader: 2 Replicas: 2,0,1 Isr: 2
只有节点 2 的所有数据都是同步的.我试过重新启动代理 0 和 1，但它并没有改善情况 - 它使情况变得更糟.我很想重新启动节点 2，但我假设它会导致停机或集群故障，所以我想尽可能避免它.
Only node 2 has all the data in-sync. I've tried restarting brokers 0 and 1 but it didn't improve the situation - it made it even worse. I'm tempted to restart node 2 but I'm assuming it will lead to downtime or cluster failure so I'd like to avoid it if possible.
我没有在日志中看到任何明显的错误，所以我很难弄清楚如何调试这种情况.任何提示将不胜感激.
I'm not seeing any obvious errors in logs so I'm having a hard time figuring out how to debug the situation. Any tips would be greatly appreciated.
谢谢！
一些附加信息...如果我检查节点 2(具有完整数据的节点)上的指标，它确实意识到某些分区未正确复制.:
Some additional info ... If I check the metrics on node 2 (the one with full data), it does realize that some partitions are not correctly replicated.:
$>get -d kafka.server -b kafka.server:type=ReplicaManager,name=UnderReplicatedPartitions *
#mbean = kafka.server:type=ReplicaManager,name=UnderReplicatedPartitions:
Value = 930;
节点 0 和 1 没有.他们似乎认为一切都很好:
Nodes 0 and 1 don't. They seem to think everything is fine:
$>get -d kafka.server -b kafka.server:type=ReplicaManager,name=UnderReplicatedPartitions *
#mbean = kafka.server:type=ReplicaManager,name=UnderReplicatedPartitions:
Value = 0;
这是预期的行为吗?
推荐答案
尝试增加 replica.lag.time.max.ms.
解释如下:
如果副本未能发送获取请求的时间超过 replica.lag.time.max.ms，则认为它已死并从 ISR 中删除.
If a replica fails to send a fetch request for longer than replica.lag.time.max.ms, it is considered dead and is removed from the ISR.
如果副本开始落后于领导者的时间超过 replica.lag.time.max.ms，则认为它太慢并从 ISR 中删除.因此，即使流量出现峰值并且大量消息写入领导者，除非副本始终保持在领导者之后的 replica.lag.time.max.ms，否则它不会在 ISR 中混入和混出.
If a replica starts lagging behind the leader for longer than replica.lag.time.max.ms, then it is considered too slow and is removed from the ISR. So even if there is a spike in traffic and large batches of messages are written on the leader, unless the replica consistently remains behind the leader for replica.lag.time.max.ms, it will not shuffle in and out of the ISR.
这篇关于Kafka 在某些节点上分区不同步的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！