search

confluentinc / schema-registry

Confluent Schema Registry for Kafka
https://docs.confluent.io/current/schema-registry/docs/index.html
Other
2.18k stars 1.11k forks source link

Health check endpoint #1267

Open sopeal opened 4 years ago

sopeal commented 4 years ago

Hello,

I think adding a health check rest endpoint that verifies connection of depending services like kafka and zookeeper would bring value to schema registry.

I have schema registry managed by kubernetes cluster and I found out that sometimes schema registry loses connection to kafka. I can fix this problem by restarting a pod. Unfortunately there is no health check endpoint so restarting cannot be done automatically by kubernetes.

Is there any other solution which resolves that problem?

chethanuk commented 4 years ago

Agree, it will help to make health check easier in K8s

mikouaj commented 4 years ago

+1

NMamont commented 4 years ago

+1

ghost commented 4 years ago

+1

msilvestre commented 4 years ago

+1

OneCricketeer commented 4 years ago

@rayokota Feel free to copy my healthCheck logic from here - https://github.com/zalando-incubator/remora/pull/62/files#diff-2e8cc252e67c2ad91fb6519cc88f0f99R86

rayokota commented 4 years ago

Thanks @cricket007, I'll take a look.

BeyondEvil commented 3 years ago

Any updates here?

OneCricketeer commented 3 years ago

What's wrong with /v1/metadata/id?

It already returns 500 error when backing store is down

rodriguezconde commented 3 years ago

Any updates on this issue? It would be nice to have some way to healthcheck schema registry within Kubernetes.

OneCricketeer commented 3 years ago

@rodriguezconde See my previous comment

zhjuncai commented 1 year ago

looks like /v1/metadata/id was protected once authentication enabled.

Is there a public endpoint that act as health check url?

alko89 commented 1 year ago

/subjects seems to be a better option

vl-kp commented 5 months ago

any update?