NoNodeAvailableException: None of the configured nodes are available

[marbetschar]

Any Idea how to fix this error? :(

Exception while waiting for cluster state: YELLOW due to
org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: []

bin/importer.sh config.json

"client.transport.ignore_cluster_name": true,
"client.transport.ping_timeout": "5s",
"client.transport.nodes_sampler_interval": "5s",
"client.transport.sniff": false,
"cluster.name": "goldncompass-dev",
"elasticsearch.hosts": "127.0.0.1:9300"

elasticsearch.yml

# Use a descriptive name for your cluster:
#
cluster.name: goldncompass-dev

# Use a descriptive name for the node:
#
node.name: Shira

# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: 127.0.0.1

Elastic search v2.3.5 logs the following:

[2016-08-12 00:01:37,316][WARN ][transport.netty          ] [Shira] exception caught on transport layer [[id: 0x73a297fa, /127.0.0.1:56407 => /127.0.0.1:9300]], closing connection
java.lang.IllegalStateException: Message not fully read (request) for requestId [0], action [cluster/nodes/info], readerIndex [39] vs expected [57]; resetting
        at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:121)

[salyh]

Try master branch and build it yourself

[salyh]

or try this one https://github.com/salyh/elasticsearch-imap/releases/tag/1.0-es2.3

[tehsphinx]

tried the zip of version 1.0-es2.3 with elasticsearch:2.3.5 and still getting "None of the configured nodes are available"

[tehsphinx]

ok works if setting following settings:

"client.transport.ignore_cluster_name": true,
"client.transport.sniff": false,

[tehsphinx]

BTW: thanks for the great work!

[salyh]

Will investigate this further

[geekpete]

With the transport client, it's best to also ensure the same exact version of java is used on both the server nodes and any clients connecting to it with the transport client protocol. With the REST client this is not an issue and can work against different elasticsearch versions in many cases as well.

[olesk75]

Also having the same issue with both 1.0-es2.3 and master, and changing parameters like tehsphinx did not help. However, I'm at 5.0.0-beta1, so that might be the reason I guess (5.0.0-beta1, Build: 7eb6260/2016-09-20T23:10:37.942Z, JVM: 1.8.0_101).

[salyh]

ES 5.0.0-x not supported yet!

[nitinsridar]

I'm AWS Elasticsearch and Transport Client for communication getting the below error, please help out if you found any solutions

"exception": "org.elasticsearch.client.transport.NoNodeAvailableException",
"message": "None of the configured nodes are available: [{#transport#-1}

[ymihay]

AWS ElasticSearch still doesn't support the Elastic Search native transport protocol. You might want to use REST based client instead.