、
这家伙太懒，什么都没留下
这家伙太懒，什么都没留下
我这边也一样，kafka的vm搬迁，上午停机，下午才启动起来，然后kafka有一个节点如果没启动，under replicated就为100%，到底啥问题哦，如何解决这种问题呢
大佬，有个问题啊我的环境是3zk，3broker的kafka集群，但是当我关掉一个节点之后，kafka的under replicaed就是变100%，而且我把topic由原来的单副本增加到3副本了，但是我手动leader选举还是失败,日志却显示已经我是leader了
[2020-08-08 19:06:21,462] INFO [Broker id=0] Skipped the become-leader state change after marking its partition as leader with correlation id 13 from controller 2 epoch 22 for partition __consumer_offsets-34 (last update controller epoch 22) since it is already the leader for the partition. (state.change.logger)
[2020-08-08 19:06:21,462] INFO [Broker id=0] Skipped the become-leader state change after marking its partition as leader with correlation id 13 from controller 2 epoch 22 for partition __consumer_offsets-15 (last update controller epoch 22) since it is already the leader for the partition. (state.change.logger)
[2020-08-08 19:06:21,463] INFO [Broker id=0] Skipped the become-leader state change after marking its partition as leader with correlation id 13 from controller 2 epoch 22 for partition __consumer_offsets-12 (last update controller epoch 22) since it is already the leader for the partition. (state.change.logger)
[2020-08-08 19:06:21,464] INFO [Broker id=0] Skipped the become-leader state change after marking its partition as leader with correlation id 13 from controller 2 epoch 22 for partition __consumer_offsets-9 (last update controller epoch 22) since it is already the leader for the partition. (state.change.logger)
[2020-08-08 19:06:21,464] INFO [Broker id=0] Skipped the become-leader state change after marking its partition as leader with correlation id 13 from controller 2 epoch 22 for partition __consumer_offsets-28 (last update controller epoch 22) since it is already the leader for the partition. (state.change.logger)
[2020-08-08 19:06:21,465] INFO [Broker id=0] Skipped the become-leader state change after marking its partition as leader with correlation id 13 from controller 2 epoch 22 for partition fluentbit.kube-0 (last update controller epoch 22) since it is already the leader for the partition. (state.change.logger)
[2020-08-08 19:06:21,466] INFO [Broker id=0] Skipped the become-leader state change after marking its partition as leader with correlation id 13 from controller 2 epoch 22 for partition __consumer_offsets-6 (last update controller epoch 22) since it is already the leader for the partition. (state.change.logger)
[2020-08-08 19:06:21,466] INFO [Broker id=0] Skipped the become-leader state change after marking its partition as leader with correlation id 13 from controller 2 epoch 22 for partition __consumer_offsets-16 (last update controller epoch 22) since it is already the leader for the partition. (state.change.logger)
[2020-08-08 19:06:21,467] INFO [Broker id=0] Skipped the become-leader state change after marking its partition as leader with correlation id 13 from controller 2 epoch 22 for partition __consumer_offsets-22 (last update controller epoch 22) since it is already the leader for the partition. (state.change.logger)
[2020-08-08 19:06:21,468] INFO [Broker id=0] Skipped the become-leader state change after marking its partition as leader with correlation id 13 from controller 2 epoch 22 for partition __consumer_offsets-3 (last update controller epoch 22) since it is already the leader for the partition. (state.change.logger)
