Denver Naidoo
Denver Naidoo

Reputation: 142

Azure functions previously known cluster id issue on Kafka Trigger

I have an Azure Function app and have a kafka trigger which works on other environments. I get this error when trying to to use a new cluster locally in a docker container. The cluster id is FaMgNL3ASkmp-GvfewNOxw. Where or how is it caching that older cluster id?

[2025-02-19T17:43:07.579Z] Libkafka: [thrd:main]: Broker GroupCoordinator/1 reports different ClusterId "bfU02MJ8Sz24p3v5pUAukQ" than previously known "JbosiV5OSVqk1UuvSu8IlA": a client must not be simultaneously connected to multiple clusters
[2025-02-19T17:43:07.591Z] Libkafka: [thrd:main]: Broker localhost:9092/bootstrap reports different ClusterId "JbosiV5OSVqk1UuvSu8IlA" than previously known "bfU02MJ8Sz24p3v5pUAukQ": a client must not be simultaneously connected to multiple clusters

Upvotes: 0

Views: 30

Answers (0)

Related Questions