Hey Team getting an error with the job `datahub-sy...
# troubleshoot
s
Hey Team getting an error with the job
datahub-system-update-job
Copy code
2023-04-15 05:00:18.721 ERROR 1 --- [ main] i.c.k.s.client.rest.RestService : Failed to send HTTP request to endpoint: http://prerequisites-cp-schema-registry:8081/subjects/DataHubUpgradeHistory_v1-value/versions
252
251
java.net.UnknownHostException: prerequisites-cp-schema-registry
250
at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:229) ~[na:na]
249
at java.base/java.net.Socket.connect(Socket.java:609) ~[na:na] 

Along with

2023-04-15 05:00:18.697 ERROR 1 --- [ main] i.c.k.s.client.rest.RestService : Failed to send HTTP request to endpoint: http://prerequisites-cp-schema-registry:8081/subjects/DataHubUpgradeHistory_v1-value/versions
460
459
java.net.UnknownHostException: prerequisites-cp-schema-registry
I am running on kubernetes any help would be greatly appreciated, thank you
πŸ” 1
πŸ“– 1
βœ… 1
l
Hey there πŸ‘‹ I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: βœ… There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? βœ… It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? Did you find a solution to your issue? ❌ Sorry you weren't able to find a solution. I'm sending you some tips on info you can provide to help the community troubleshoot. Whenever you feel your issue is solved, please react βœ… to your original message to let us know!
s
@astonishing-answer-96712 have you seen this issue before?
the logs from my
prerequisites-cp-schema-registry
are
Copy code
VM settings:
Max. Heap Size (Estimated): 13.62G
Ergonomics Machine Class: server
Using VM: OpenJDK 64-Bit Server VM
Does this mean that the schema registry is running?
a
I think it’s at least started, but i’m unsure if it’s running- it may be related to memory allocation on the pre-reqs, but @brainy-tent-14503 can speak more to that
b
Looks like schema registry is not running or is perhaps using a different service name in your environment. It should have logs like this, depending on the specific version.
Copy code
2023-04-18 15:33:22 [2023-04-18 20:33:22,380] INFO Started @2270ms (org.eclipse.jetty.server.Server)
2023-04-18 15:33:22 [2023-04-18 20:33:22,381] INFO Schema Registry version: 7.2.2 commitId: c7b8fa7d428ef426d7c6aaefa04b734cf117580e (io.confluent.kafka.schemaregistry.rest.SchemaRegistryMain)
2023-04-18 15:33:22 [2023-04-18 20:33:22,381] INFO Server started, listening for requests... (io.confluent.kafka.schemaregistry.rest.SchemaRegistryMain)
Secondly there should be a k8 service and for it and the name of the service should indicate the correct hostname from within the k8 cluster. Get the services like
kubectl get svc