Hi team,
I'm currently deploying datahub on kubern...
# troubleshoota
adorable-magazine-49274
12/01/2022, 2:39 PMHi team,
I'm currently deploying datahub on kubernetes via quickstart.
Currently, the following error occurs in the pod called
datahub-elasticsearch-setup-job Copy code
Problem with request: Get <http://elasticsearch-master:9200>: dial tcp 10.102.226.215:9200: connect: connection refused. Sleeping 1sadorable-magazine-49274
12/01/2022, 2:40 PMAdditionally, here's a quickstart I ran.
Copy code
minikube start --kubernetes-version=v1.19.0 --memory=8gb --cpus=8
$ kubectl create secret generic mysql-secrets \
$ --from-literal=mysql-root-password=datahub
$ kubectl create secret generic neo4j-secrets \
$ --from-literal=neo4j-password=datahub
$ helm repo add datahub <https://helm.datahubproject.io/>
$ helm install prerequisites datahub/datahub-prerequisites
$ helm install datahub datahub/datahubb
brainy-tent-14503
12/01/2022, 5:15 PMCan you return the results of the following.
kubectl get poa
adorable-magazine-49274
12/02/2022, 4:33 AMI will share k9s results here.
adorable-magazine-49274
12/02/2022, 4:34 AMAdditionally, does the setting of namespaces affect this process?
adorable-magazine-49274
12/02/2022, 4:53 AMThe elasticsearch-master pod had the following error message:
Copy code
{"type": "server", "timestamp": "2022-12-02T06:21:06,748Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-0", "message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [elasticsearch-master-0, elasticsearch-master-1, elasticsearch-master-2] to bootstrap a cluster: have discovered [{elasticsearch-master-0}{6bKcgTeSRoGLgVn8xAwlEQ}{6aJ7uVm4TVev_4fVewkLGg}{172.17.0.7}{172.17.0.7:9300}{cdfhilmrstw}]; discovery will continue using [] from hosts providers and [{elasticsearch-master-0}{6bKcgTeSRoGLgVn8xAwlEQ}{6aJ7uVm4TVev_4fVewkLGg}{172.17.0.7}{172.17.0.7:9300}{cdfhilmrstw}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }
{"type": "server", "timestamp": "2022-12-02T04:50:25,140Z", "level": "WARN", "component": "r.suppressed", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-0", "message": "path: /_cluster/health, params: {wait_for_status=green, timeout=1s}",
"stacktrace": ["org.elasticsearch.discovery.MasterNotDiscoveredException: null",…b
brainy-tent-14503
12/02/2022, 4:24 PMThe master pod is waiting for the other pending pods to do leader elections since the replica is set to 3. You have a couple options here. The first is to describe the pending pods (-1 & -2) to see why they are pending and not running. The second is to only run a single elasticsearch node. The latter isn’t too crazy since this is a local non-production setup. In order to do the latter there are a few settings in the prerequisites chart to set when running with 1 elasticsearch replica, see these notes. (lines 5 - 12)
7 Views