Connector UNASSIGNED

[joohy]

If one specific broker in the kafka cluster is taken down, the state of all connectors becomes unassigned.

Even if other brokers are down, the status of the connectors is normal.

There is no error log.
Do you know what kind of case this is?

The specific broker is the kafka-broker-05 server.
#connect-distributed.properties

bootstrap.servers=kafka-broker-01:9092,kafka-broker-02:9092,kafka-broker-03:9092,kafka-broker-04:9092,kafka-broker-05:9092
group.id=connect-cluster
key.converter=org.apache.kafka.connect.storage.StringConverter
value.converter=io.confluent.connect.avro.AvroConverter
key.converter.schemas.enable=false
value.converter.schemas.enable=false
value.converter.schema.registry.url=http://schema-registry-01:8081
offset.storage.topic=connect-offsets
offset.storage.replication.factor=3
offset.storage.topic=connect-offsets
offset.storage.replication.factor=3
config.storage.topic=connect-configs
config.storage.replication.factor=3
status.storage.topic=connect-status
status.storage.replication.factor=3
offset.flush.interval.ms=10000
plugin.path=/usr/share/java
connector.client.config.override.policy=All
topic.creation.enable=false

[rick]

@joohy can you clarify please? You mention these two things:

@joohy

the state of all connectors becomes unassigned.

And

Even if other brokers are down, the status of the connectors is normal.

I’m not certain how you’re determining and what connector status you’re observing.

I know you said there were no error logs, but searching for and providing any WARN or ERROR logging in brokers or connect workers would help someone assist.