failed to get node info using native transport

881 views
Skip to first unread message

刘凯祥

unread,
Nov 28, 2016, 1:37:51 AM11/28/16
to clojure-elasticsearch
Hi Everybody,

I setup a cluster of elaticsearch that it includes three nodes. Elaticsearch version is 2.4.1.

The elaticsearch configuration of one node looks like as:
cluster.name: es_cluster
node.name: es_node1
path.repo: ["/mnt/backups/backup"]
network.host: 192.168.1.104
discovery.zen.ping.unicast.hosts: ["192.168.1.104", "192.168.1.105", "192.168.1.106"]

Now, I want to use the native transport to connect to the ES cluster but I get "failed to get node info" error message after I run below code:
(def conn (es/connect  [["192.168.1.104" 9300] ["192.168.1.105" 9300] ["192.168.1.106" 9300]] {"cluster.name" "es_cluster"}))

The detail error message is:
INFO [2016-11-28 01:11:28,063] elasticsearch[Aldebron][generic][T#2] - org.elasticsearch.client.transport - [Aldebron] failed to get node info for [#transport#-1][localhost.localdomain][inet[/192.168.1.104:9300]], disconnecting...
org.elasticsearch.transport.NodeDisconnectedException: [][inet[/192.168.1.104:9300]][cluster:monitor/nodes/info] disconnected
INFO [2016-11-28 01:11:28,066] elasticsearch[Aldebron][generic][T#2] - org.elasticsearch.client.transport - [Aldebron] failed to get node info for [#transport#-2][localhost.localdomain][inet[/192.168.1.105:9300]], disconnecting...
org.elasticsearch.transport.NodeDisconnectedException: [][inet[/192.168.1.105:9300]][cluster:monitor/nodes/info] disconnected
INFO [2016-11-28 01:11:28,067] elasticsearch[Aldebron][generic][T#2] - org.elasticsearch.client.transport - [Aldebron] failed to get node info for [#transport#-3][localhost.localdomain][inet[/192.168.1.106:9300]], disconnecting...

Who can help me or give some hint for the issue? Thanks you very much.
Also, I don't find firewall issue for the three ES nodes from client and the 9300 port of three nodes are openned.


Thanks
Ray

Henrik Lundahl

unread,
Nov 28, 2016, 4:39:08 PM11/28/16
to Elastisch
Hi

Is port 9300 open for both TCP and UDP?


BR

--
Henrik


--
Documentation guides: http://clojureelasticsearch.info
Repository: https://github.com/clojurewerkz/elastisch
Change log: https://github.com/clojurewerkz/elastisch/blob/master/ChangeLog.md
Issues: https://github.com/clojurewerkz/elastisch/issues
---
Has recibido este mensaje porque estás suscrito al grupo "clojure-elasticsearch" de Grupos de Google.
Para cancelar la suscripción a este grupo y dejar de recibir sus mensajes, envía un correo electrónico a clojure-elasticsearch+unsub...@googlegroups.com.
Para acceder a más opciones, visita https://groups.google.com/d/optout.

刘凯祥

unread,
Nov 28, 2016, 7:38:15 PM11/28/16
to clojure-elasticsearch
thanks a lot..

In my machine:
[root@es_node1 ~]# netstat -tcpln|grep 9300
tcp6       0      0 192.168.1.104:9300      :::*                    LISTEN      2048/java           
tcp6       0      0 192.168.1.104:9300      :::*                    LISTEN      2048/java           
tcp6       0      0 192.168.1.104:9300      :::*                    LISTEN      2048/java           
^C
[root@es_node1 ~]# 
[root@es_node1 ~]# 
[root@es_node1 ~]# netstat -tupln|grep 9300
tcp6       0      0 192.168.1.104:9300      :::*                    LISTEN      2048/java           
[root@es_node1 ~]# 

But , how to open 9300 both tcp and udp?


在 2016年11月29日星期二 UTC+8上午5:39:08,Henrik Lundahl写道:

Henrik Lundahl

unread,
Nov 30, 2016, 1:27:17 PM11/30/16
to Elastisch
Hmm, I'm not sure it's needed... I think you should:

* Check the ES logs.
* Check the version of the Java client. Using the same version as the ES servers is safest.
* Try with just one node.


BR

--
Henrik



--
Henrik


Para cancelar la suscripción a este grupo y dejar de recibir sus mensajes, envía un correo electrónico a clojure-elasticsearch+unsubscri...@googlegroups.com.

Para acceder a más opciones, visita https://groups.google.com/d/optout.

Jin Wang

unread,
Dec 29, 2016, 8:56:53 PM12/29/16
to clojure-elasticsearch
Not sure if your have solved your problem.   i met similar issue when my client API version was different with the ES cluster version.

刘凯祥

unread,
Jan 3, 2017, 7:58:57 PM1/3/17
to clojure-elasticsearch

Thanks a lot, I solved this problem by change my  ES cluster version to 3.* and it worked.and I tried 1.7* version, it also worked. When using 2.x, this problem occured.
Thank you all the same.


在 2016年12月30日星期五 UTC+8上午9:56:53,Jin Wang写道:
Reply all
Reply to author
Forward
0 new messages