confluentinc/schema-registry

If kafka is down schema registry pod not restarted to sync-up with kafka, it's failed with error. Any possible solution for this.

saurabh1073 opened this issue · 2 comments

saurabh1073 commented

Due to any reason if kafka pod is down then schema registry failed with error "_schema topic not available and unable to write to kafka store". So just to check wether kafka up or not added httpGet: /subjects in liveness and readiness probe but once kafka down its failed with error unable to connect with kafka and this liveness and readiness probe not checked that's why schema registry pod not restarted to syncup and see wether kafka is up or not. Please suggest any way to check this or any possible solution for this.

drozd0 commented

I suppose it's related to your question: #3192

OneCricketeer commented

The HTTP server hits an in-memory cache.

I think it would be better to use an exec-based k8s probe to run kafka-topics --describe --topic _schemas