Kafka Connect - Dead workers going in cyclic mode about kafka-connect-storage-cloud

[ismail261]

I think i found what i was doing wrong on my side. All the status values that got repopulated came from same group id which was running in different cluster with worker ids which were not accessible in this current cluster.

Changing the group id registered all the connectors in new group giving current worker id's which made them start without any issues.

I just think if there was better way to identify those issues and throw out the error on console saying what might be happening.

[kkonstantine]

This doesn't seem specific to this connector.

Did you delete all 3 internal topics that Connect uses to track metadata?

If that's what you intended to do, these topics are defined by the value of the following properties in the worker's config:
offset.storage.topic
config.storage.topic
status.storage.topic

[sheu]

I think i found what i was doing wrong on my side. All the status values that got repopulated came from same group id which was running in different cluster with worker ids which were not accessible in this current cluster.

Changing the group id registered all the connectors in new group giving current worker id's which made them start without any issues.

I just think if there was better way to identify those issues and throw out the error on console saying what might be happening.

How did you change the groupId?