客户端无法发布，因为具有完整复制因子的防火墙问题 [英] Client cannot pubish because firewall issue with full replication factor

问题描述

设置:运行版本2.12-2.3.0的三节点Kafka群集.复制因子是3，每个主题有20个分区.

说明:Kafka群集中的所有三个节点之间都可以相互通信而不会出现问题.Kafka客户端引入了不正确的防火墙，该防火墙阻止"了防火墙.客户端与一个Kafka节点进行通信.客户端无法再发布到任何Kafka节点.两个Kafka节点仍然可以从Kafka客户端网络访问.我们了解这是一个网络裂脑问题.

问题:是否有一种配置Kafka的方法，以便Kafka客户端可以与幸存"客户端通信.卡夫卡节点?

解决方案

客户端无法再发布到任何Kafka节点

这不应该发生.客户端应该只能与该节点上的 leader分区通信，而不能继续与另一个可达节点上的Leader分区通信.

如果出现客户端的主机网络/防火墙，则无法在服务器端进行任何更改.

Setup: Three Node Kafka cluster running version 2.12-2.3.0. Replication factor is 3 and with 20 partition per topic.

Description: All three nodes in Kafka cluster can communicate between themself without issue. An incorrect firewall is introduced with Kafka client which "block" client from communicating with one Kafka node. The client can no longer publish to any of the Kafka node. Two Kafka nodes are still network reachable from Kafka client. We understand this is a network split brain issue.

Question: Is there a way to configure Kafka so that kafka client can communicate with "surviving" Kafka nodes?

解决方案

The client can no longer publish to any of the Kafka node

That shouldn't happen. The client should only be unable to communicate with leader partitions on that one node, and continue communicating with the leader partitions on the other, reachable nodes.

There are no changes you could make on the server-side if the client's host network/firewall is the issue.

这篇关于客户端无法发布，因为具有完整复制因子的防火墙问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！