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

问题描述

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

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

说明:Kafka 集群中的所有三个节点都可以毫无问题地相互通信.Kafka 客户端引入了一个不正确的防火墙，它阻止"了客户端.客户端与一个 Kafka 节点通信.客户端不能再发布到任何 Kafka 节点.两个 Kafka 节点仍然可以从 Kafka 客户端通过网络访问.我们知道这是网络裂脑问题.

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.

问题:有没有办法配置 Kafka 以便 kafka 客户端可以与幸存"的客户端通信?Kafka 节点?

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

推荐答案

客户端不能再发布到任何Kafka节点

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屋！