You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "lqjacklee (Jira)" <ji...@apache.org> on 2020/12/09 01:51:00 UTC
[jira] [Assigned] (KAFKA-10824) Connection to node -1 could not be
established. Broker may not be available.
[ https://issues.apache.org/jira/browse/KAFKA-10824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lqjacklee reassigned KAFKA-10824:
---------------------------------
Assignee: lqjacklee
> Connection to node -1 could not be established. Broker may not be available.
> ----------------------------------------------------------------------------
>
> Key: KAFKA-10824
> URL: https://issues.apache.org/jira/browse/KAFKA-10824
> Project: Kafka
> Issue Type: Bug
> Components: consumer, KafkaConnect, network, offset manager
> Affects Versions: 2.0.0, 2.1.1
> Reporter: Mohammad Abboud
> Assignee: lqjacklee
> Priority: Blocker
>
> After a specific running time, the consumer groups will become inactive, while trying to reset the offsets, I get the message "*Connection to node -1 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)*".
> My work around is to delete all the *consumer_offsets* folders and restart the server.
> below is the content of server.properties:
> listeners=PLAINTEXT://0.0.0.0:9092
> advertised.listeners=PLAINTEXT://Server01:9092
--
This message was sent by Atlassian Jira
(v8.3.4#803005)