Cluster information:
kubectl version
Client Version: version.Info{Major:“1”, Minor:“13”, GitVersion:“v1.13.2”, GitCommit:“cff46ab41ff0bb44d8584413b598ad8360ec1def”, GitTreeState:“clean”, BuildDate:“2019-01-10T23:35:51Z”, GoVersion:“go1.11.4”, Compiler:“gc”, Platform:“darwin/amd64”}
Server Version: version.Info{Major:“1”, Minor:“10”, GitVersion:“v1.10.11”, GitCommit:“637c7e288581ee40ab4ca210618a89a555b6e7e9”, GitTreeState:“clean”, BuildDate:“2018-11-26T14:25:46Z”, GoVersion:“go1.9.3”, Compiler:“gc”, Platform:“linux/amd64”}
Cloud being used: Openstack
Installation method:
Host OS: Linux
CNI and version:
CRI and version:
Hello,
I am working on getting an Elastic Search cluster in Kubernetes but I am getting the following on the data pods, I know it can be related with the service but I cannot find anything that really points me in one direction. Thanks in advance for any help
Readiness probe failed: Get http://100.100.2.3:9200/_cluster/health: dial tcp 100.100.2.3:9200: getsockopt: connection refused
When I go to the log of the pod I get this:
{“type”: “server”, “timestamp”: “2019-07-15T14:23:58,918+0000”, “level”: “WARN”, “component”: “o.e.c.c.ClusterFormationFailureHelper”, “cluster.name”: “petelk”, “node.name”: “elasticsearch-data-0”, “message”: “master not discovered yet: have discovered [{elasticsearch-master-5fd58b954-4znb7}{QK1RS9lmTvu_lI6fgoMf5A}{vQV2h8FNRcuOObAgUWJpFQ}{100.100.0.4}{100.100.0.4:9300}{ml.machine_memory=1073741824, ml.max_open_jobs=20, xpack.installed=true}, {elasticsearch-master-5fd58b954-ch5hx}{qoexMLTHRCSR06_F5fhASg}{LF8pxP2FRuOj3TRqZfM-uQ}{100.100.2.2}{100.100.2.2:9300}{ml.machine_memory=1073741824, ml.max_open_jobs=20, xpack.installed=true}]; discovery will continue using [100.100.0.4:9300, 100.100.2.2:9300] from hosts providers and [{elasticsearch-data-0}{q7C0rcR-QUSuaXK3oAhq5g}{NfZOVXLURjCqXc5JdZKPxg}{100.100.2.3}{100.100.2.3:9300}{ml.machine_memory=8589934592, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0” }
Here an output of some important info:
NAME READY STATUS RESTARTS AGE
elasticsearch-data-0 0/1 Running 0 2d
elasticsearch-master-5fd58b954-4znb7 1/1 Running 0 2d
elasticsearch-master-5fd58b954-ch5hx 1/1 Running 0 2d
kubectl get services --namespace elk
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
access-elasticsearch-master ClusterIP 198.18.226.40 9200/TCP,9300/TCP 2d
elasticsearch ClusterIP None 9200/TCP,9300/TCP 2d
elasticsearch-master ClusterIP None 9200/TCP,9300/TCP 2d