Connectivity issues with a new/upgraded 2.X cluster? Read here first :)

(Mark Walkom) #1

If you are having issues with nodes not forming a cluster, or if you are unable to connect to a remote cluster, please read this first!

In Elasticsearch 2.0 we made some major changes to the way default networking is configured.

The primary one is that Elasticsearch no longer listens to all interfaces by default, and instead only binds to loopback/127.00.1. This means that if you are coming from 1.X you will need to explicitly set in your elasticsearch.yml config file.

The second is that multicast discovery has been removed as the default discovery method and is now available via a plugin only.

For more information, please read the release notes, here.

Remote access elasticsearch 9200 fails
Querying Elasticsearch Remotely
Elasticsearch unavailable during upgrade
How do you install Marvel in windows?
(Mark Walkom) #2

(Mark Walkom) #3

(riki) #4


I started using ES 2.0. In elasticsearch.yml file I have set as host name.

I see lots of exception as below:

[2016-01-23 09:01:02,388][WARN ][cluster.service ] [Mangle] failed to reconnect to node {Gee}{MtDkhr9rSza5QoSqKTqkrA}{}{}{data=false, client=true}
ConnectTransportException[[Gee][] connect_timeout[30s]]; nested: ConnectException[Connection refused: no further information: /];
at org.elasticsearch.transport.netty.NettyTransport.connectToChannels(
at org.elasticsearch.transport.netty.NettyTransport.connectToNode(
at org.elasticsearch.transport.netty.NettyTransport.connectToNode(
at org.elasticsearch.transport.TransportService.connectToNode(
at org.elasticsearch.cluster.service.InternalClusterService$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: Connection refused: no further information: /
at Method)
at org.jboss.netty.util.internal.DeadLockProofWorker$
... 3 more

I am not sure why transport client is still trying to connect to even after setting I also tried setting as host name but no luck.

What am I doing wrong?


(Mark Walkom) #5

It'd help if you provided the relevant config sections.

(riki) #6

Hi Mark,

Here is the settings that I have put in elasticsearch.yml. TESTCLUSTER
transport.tcp.port: 9300
http.port: 9200
http.enabled: false false
index.fielddata.cache: node
indices.fielddata.cache.size: 1m
indices.cache.filter.size: 1m
threadpool.bulk.type: fixed
threadpool.bulk.queue_size: 8000

In log i see the following while starting up

[2016-01-23 08:52:59,603][INFO ][node ] [Mangle] version[2.0.0], pid[1844], build[de54438/2015-10-22T08:09:48Z]
[2016-01-23 08:52:59,605][INFO ][node ] [Mangle] initializing ...
[2016-01-23 08:52:59,942][INFO ][plugins ] [Mangle] loaded [], sites []
[2016-01-23 08:53:00,337][INFO ][env ] [Mangle] using [1] data paths, mounts [[(C:)]], net usable_space [82.1gb], net total_space [99.6gb], spins? [unknown], types [NTFS]
[2016-01-23 08:53:08,744][INFO ][node ] [Mangle] initialized
[2016-01-23 08:53:08,745][INFO ][node ] [Mangle] starting ...
[2016-01-23 08:53:09,702][INFO ][transport ] [Mangle] publish_address {}, bound_addresses {}
[2016-01-23 08:53:09,744][INFO ][discovery ] [Mangle] TESTCLUSTER/CYoSCFfaRMSPvb9zvn0KCw
[2016-01-23 08:53:19,141][INFO ][cluster.service ] [Mangle] detected_master {Ankhi}{SEMYv5YIQQ27KQMywDxcjQ}{}{}, added {{Laura Dean}{bme0NfOERmC4qkRz4PEt3A}{}{}{data=false, client=true},{Air-Walker}{kGeX3KnXSG2Mqv7shVeKGQ}{}{},{Gee}{MtDkhr9rSza5QoSqKTqkrA}{}{}{data=false, client=true},{Fault Zone}{Girj3ldxQgacdj-SHNim6w}{}{}{data=false, client=true},{Ankhi}{SEMYv5YIQQ27KQMywDxcjQ}{}{},}, reason: zen-disco-receive(from master [{Ankhi}{SEMYv5YIQQ27KQMywDxcjQ}{}{}])
[2016-01-23 08:53:20,315][WARN ][cluster.service ] [Mangle] failed to connect to node [{Gee}{MtDkhr9rSza5QoSqKTqkrA}{}{}{data=false, client=true}]


(Mark Walkom) #7

Well it's connecting to a valid interface.

I'd suggest you create a separate thread and ask, I don't think this is a settings issue related to the original post.

2 nodes with the same cluster but in configured in different machines
Nodes discovery after upgrading from 1.7.1 to 2.2.0
Nearly All Indices UNASSIGNED and All Are Red
(Python Coder) #8

are you sure that the host resolution evaluates to the Non-loopback IP address on node Gee?

Unable to RUN bulk API client from different server -- NoNodeAvailableException
(system) #9