"could not receive: [6] Not Leader For Partition: the client attempted to send messages to a replica that is not the leader for some partition, the client's metadata are likely out of date:

[anil9030]

one of our micro services (Metadata Change Detection) has been not able to create topics until we restarted that pod.
any idea why this error showed in logs

[scholzj]

AFAIK, That suggests that the client had stale metadata about the Kafka cluster.

[scholzj]

Thi leadership can change in the Kafka cluster for various reasons. The client should normally detect it (from errors like this), update the metadata and continue. So I'm not sure seeing this error itself is an issue. But it should normally recover from this automatically without restarting the pods.

[anil9030]

can you review this error in external kafka setup RedHatInsights/edge-api#469
seems like they found some fix for it but can that be implemented here in strimzi

[scholzj]

Sorry, I'm not sure I see the relationship.

[anil9030]

shall i raise an issue with this? here?

[scholzj]

As I said, I think this is an issue of the client, not Strimzi.