I am deploying the elastic search cluster in self hosted kubernetes cluster. I am getting the below error message in elastic search cluster master pods.
Compute resource of elasticsearch cluster vm -
RAM - 8GB CPU - 4vCPU
Name resolution is happening when i am connecting the elastic search master pod using its fqdn elasticsearch-cluster-es-master-0.elasticsearch-cluster-es-master.elastic-system.svc.cluster.local from other pods but when i am connecting using the elasticsearch-cluster-es-master-0.elasticsearch-cluster-es-master.elastic-system.svc then fqdn is not resolving to its ip address.
Normally cluster.local should automatically appended when doing the nslookup of elasticsearch-cluster-es-master-0.elasticsearch-cluster-es-master.elastic-system.svc
{"@timestamp":"2025-02-08T13:39:28.790Z", "log.level":"ERROR", "message":"fatal exception while booting Elasticsearch", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.bootstrap.Elasticsearch","elasticsearch.cluster.uuid":"o6L3JYK3S6K4BPPPjk8Ebg","elasticsearch.node.id":"erKZEAM9TtqJhUZHsUlVJw","elasticsearch.node.name":"elasticsearch-cluster-es-master-0","elasticsearch.cluster.name":"elasticsearch-cluster","error.type":"org.elasticsearch.transport.BindTransportException","error.message":"Failed to resolve publish address","error.stack_trace":"org.elasticsearch.transport.BindTransportException: Failed to resolve publish address\n\tat org.elasticsearch.server@8.16.1/org.elasticsearch.http.AbstractHttpServerTransport.bindServer(AbstractHttpServerTransport.java:201)\n\tat org.elasticsearch.transport.netty4@8.16.1/org.elasticsearch.http.netty4.Netty4HttpServerTransport.doStart(Netty4HttpServerTransport.java:231)\n\tat org.elasticsearch.server@8.16.1/org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:51)\n\tat org.elasticsearch.server@8.16.1/org.elasticsearch.node.Node.start(Node.java:426)\n\tat org.elasticsearch.server@8.16.1/org.elasticsearch.bootstrap.Elasticsearch.start(Elasticsearch.java:445)\n\tat org.elasticsearch.server@8.16.1/org.elasticsearch.bootstrap.Elasticsearch.initPhase3(Elasticsearch.java:255)\n\tat org.elasticsearch.server@8.16.1/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:75)\nCaused by: java.net.UnknownHostException: elasticsearch-cluster-es-master-0.elasticsearch-cluster-es-master.elastic-system.svc: Temporary failure in name resolution\n\tat java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)\n\tat java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:52)\n\tat java.base/java.net.InetAddress$PlatformResolver.lookupByName(InetAddress.java:1221)\n\tat java.base/java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1817)\n\tat java.base/java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:1149)\n\tat java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1807)\n\tat java.base/java.net.InetAddress.getAllByName(InetAddress.java:1676)\n\tat org.elasticsearch.server@8.16.1/org.elasticsearch.common.network.NetworkService.resolveInternal(NetworkService.java:267)\n\tat org.elasticsearch.server@8.16.1/org.elasticsearch.common.network.NetworkService.resolveInetAddresses(NetworkService.java:215)\n\tat org.elasticsearch.server@8.16.1/org.elasticsearch.common.network.NetworkService.resolvePublishHostAddresses(NetworkService.java:167)\n\tat org.elasticsearch.server@8.16.1/org.elasticsearch.http.AbstractHttpServerTransport.bindServer(AbstractHttpServerTransport.java:199)\n\t... 6 more\n"}
We are deploying the elastic search cluster and getting the temporary name resolution issue in elastic logs. So, Elastic Search pod is not starting up.
Elastic Search v8.16.0 is deployed in kubernetes v1.28.12.
elasticsearchkubernetes
