You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "zou shengfu (Jira)" <ji...@apache.org> on 2023/04/10 08:22:00 UTC
[jira] [Updated] (KAFKA-14885) Client can connect to broker and broker can not connect zookeeper
[ https://issues.apache.org/jira/browse/KAFKA-14885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zou shengfu updated KAFKA-14885:
--------------------------------
Description:
When a broker has some issues about network, the broker can not connect to zookeeper and controller.At this time, we replace this broker with a new broker that has a same `broker.id` with fault broker, and we can not stop the Kafka process on fault broker because of network issue. So the client can still connect this broker and can produce and consume messages normally. But the data on fault broker maybe be lost because there are some leader for partitions on the fault broker.
Do we have any good idea to solve this problem?
> Client can connect to broker and broker can not connect zookeeper
> -----------------------------------------------------------------
>
> Key: KAFKA-14885
> URL: https://issues.apache.org/jira/browse/KAFKA-14885
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 3.3.2
> Reporter: zou shengfu
> Assignee: zou shengfu
> Priority: Major
>
> When a broker has some issues about network, the broker can not connect to zookeeper and controller.At this time, we replace this broker with a new broker that has a same `broker.id` with fault broker, and we can not stop the Kafka process on fault broker because of network issue. So the client can still connect this broker and can produce and consume messages normally. But the data on fault broker maybe be lost because there are some leader for partitions on the fault broker.
> Do we have any good idea to solve this problem?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)