# Connector UNASSIGNED

**URL:** <https://forum.confluent.io/t/connector-unassigned/3763>\
**Category:** Kafka Connect\
**Created:** [27 December 2021 01:54 UTC](https://forum.confluent.io/t/connector-unassigned/3763 "2021-12-27T01:54:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![joohy](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/joohy/32/996_2.png) [@joohy](https://forum.confluent.io/u/joohy)\
**Post date:** [27 December 2021 01:54 UTC](https://forum.confluent.io/t/connector-unassigned/3763/1 "2021-12-27T01:54:33Z")

</div>

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

```auto
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

```

---

<div class="post-metadata">

**Author:** ![rick](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/rick/32/49_2.png) [@rick](https://forum.confluent.io/u/rick)\
**Post date:** [28 December 2021 16:28 UTC](https://forum.confluent.io/t/connector-unassigned/3763/2 "2021-12-28T16:28:34Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/confluentcommunity/original/1X/c49438c90c9df282e9996fdf6971be890c71b65a.svg) [@system](https://forum.confluent.io/u/system)\
**Post date:** [27 January 2022 16:29 UTC](https://forum.confluent.io/t/connector-unassigned/3763/3 "2022-01-27T16:29:33Z")

</div>

Closed on 27 January 2022 16:29 UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.