Using spring-boot-starter-web jar to connect elastic search is causing issue NoNodeAvailableException [DATAES-339]

[spring-projects-issues]

Sagar Mummidivarapu opened DATAES-339 and commented

I am using spring-boot-starter-web jar in my pom to connect Elastic Search using ElasticSearchRepository<T,T> but getting exception at commandLineRunner

Caused by: org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{127.0.0.1}{127.0.0.1:9300}]

I am using following versions:
Spring Boot Version: 1.5.2 (spring boot starter parent)
Elastic Search : 5.2.2

Same code is working if I point to Elastic Search version 2.4.4

1. Any insight why the "spring-boot-starter-data-elasticsearch" not working with latest elastic versions?
2. In future every time we upgrade to latest version of ES, should we wait for latest version of "spring-boot-starter-data-elasticsearch" that is compatible?
3. Exception like "NoNodeAvailableException" is not clear when the real issue is with ES version compatibility.

Please address these issues at the earliest and highly appreciated for the prompted response.

Also, Please find the attached project. (Excluded target folder due to size restriction in JIRA)

---

Attachments:

• Elastic-NoTarget.zip (75.88 kB)

0 votes, 5 watchers

[spring-projects-issues]

Sagar Mummidivarapu commented

any update on this please?

[spring-projects-issues]

cong wang commented

I encounter the same problem. I think it's elasticsearch's problem, check out this

[spring-projects-issues]

Tyler Eastman commented

The version of Spring Data Elasticsearch within Spring Boot version 1.5.2 doesn't support Elasticsearch 5+

https://github.com/spring-projects/spring-data-elasticsearch/wiki/Spring-Data-Elasticsearch---Spring-Boot---version-matrix

Support for Elasticsearch 5 is being added into Spring Data Elasticsearch 3+

[spring-projects-issues]

Daniel Lotz commented

I get this error as well on a 3 node elastic search service running server version 6.2.4 and on clients 5.6.9 and 6.2.4. It happens when I scale up my micro services to multiple pods or start up when another pod has recently been connected. I am starting to think that it is associated with how the client identifies themselves but I have nothing to back this up. From my experience waiting between deployments or killing the pod before deploying another solves the issue

[spring-projects-issues]

Artur Konczak commented

Hi Sagar Mummidivarapu, cong wang, Tyler Eastman, StubbornRobot

This error is related to incompatibility between client and server - please check version matrix:
https://github.com/spring-projects/spring-data-elasticsearch#elasticsearchrepository (above this link)

Logs from server:

[2018-11-09T14:32:42,034][WARN ][o.e.t.n.Netty4Transport  ] [Bh4DaO7] exception caught on transport layer [[id: 0x943e84eb, L:/127.0.0.1:9300 - R:/127.0.0.1:47208]], closing connection
java.lang.IllegalStateException: Received message from unsupported version: [2.0.0] minimal compatible version is: [5.0.0]
	at org.elasticsearch.transport.TcpTransport.messageReceived(TcpTransport.java:1323) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.transport.netty4.Netty4MessageChannelHandler.channelRead(Netty4MessageChannelHandler.java:74) ~[transport-netty4-5.2.2.jar:5.2.2]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:363) [netty-transport-4.1.7.Final.jar:4.1.7.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:349) [netty-transport-4.1.7.Final.jar:4.1.7.Final]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:341) [netty-transport-4.1.7.Final.jar:4.1.7.Final]

Logs from app/client:

java.lang.IllegalStateException: Failed to execute CommandLineRunner
	at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:779) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE]
	at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:760) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE]
	at org.springframework.boot.SpringApplication.afterRefresh(SpringApplication.java:747) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1162) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1151) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE]
	at com.art.elastic.ElasticLibApplication.main(ElasticLibApplication.java:70) [classes/:na]
Caused by: org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{127.0.0.1}{127.0.0.1:9300}]
	at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:326) ~[elasticsearch-2.4.4.jar:2.4.4]
	at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:223) ~[elasticsearch-2.4.4.jar:2.4.4]

ES transport client can only work with the same version of server - in your case you can connect to any server with version 2.x.
To connect to ES 5.x server - please use springe-data-elasticsearch in version of 3.0.x.

Also please check spring boot configuration/change log to find out what version of springe-data-elasticsearch they are using.