2023/05/08 09:30:02 Waiting for: <tcp://prerequisites-mysql.datahub-temp:3306>
2023/05/08 09:30:02 Waiting for: tcp://*****-kafka-bootstrap:9092
2023/05/08 09:30:02 Waiting for: http://*****@datahub-elasticsearch-*****:9200
2023/05/08 09:30:02 Waiting for: http:
2023/05/08 09:30:02 Problem with request: Get http:: http: no Host in request URL. Sleeping 1s
2023/05/08 09:30:02 Connected to tcp://*****-kafka-bootstrap:9092
2023/05/08 09:30:02 Received 200 from http://*****@datahub-elasticsearch-*****:9200
2023/05/08 09:30:02 Connected to <tcp://prerequisites-mysql.datahub-temp:3306>
2023/05/08 09:30:03 Problem with request: Get http:: http: no Host in request URL. Sleeping 1s

Based on previous posts, despite using

graph_service_impl: elasticsearch

the gms is somehow still waiting for

neo4j

service to start. Any way to disable this?

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? ✅ button ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? ✅ button 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!

1. v0.10.2 2. Helm Charts 3. logs shared above (

Get http:: http: no Host in request URL.

)

This seems like a configuration issue, where are you seeing that it's waiting on Neo4J? Not seeing posts about this nor should it happen, when the graph service implementation is set to ElasticSearch, Neo4J components do not load. The log you posted is coming from GMS? Have you inspected the deployment using

describe

to make sure the ENV looks right?

Hey @orange-night-91387, thanks for the response. The log is from GMS and the ENV looks fine. We are deploying the prerequisites components separately, without using the helm that was provided. Should we have mentioned that Neo4J is not required explicitly in the datahub helm? like

neo4j-community:
  enabled: false

Is there a reason you can't utilize the provided charts? With customized charts it could be some missed properties, but yes you should explicitly disable Neo4J if it is starting up in your environment. To confirm on the GMS ENV, you have:

GRAPH_SERVICE_IMPL=elasticsearch

with this GMS should not do anything with Neo4J.

Fixed it. It was a GMS version issue. Pulled the latest from docker and it stopped expecting Neo4J.