Nodes not joining cluster

ajan · June 27, 2012, 5:54am

I have an ES cluster with 5 nodes on different SLES VM's. I keep
getting this error when I start the ES nodes and they don't form a
cluster

[2012-06-27 01:38:54,052][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Wildside][lcw2NIVjTr-
KfreUoPE0yg][inet[/10.247.24.194:9300]]{data=false}], master
[[Wildside][lcw2NIVjTr-KfreUoPE0yg][inet[/10.247.24.194:9300]]
{data=false}], cluster_name[losaq-es-cluster-afzal]} with no matching
id [1]
[2012-06-27 01:38:54,051][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Douglas Ramsey]
[i6ypp9DSQoO3FQ6WXLwe1Q][inet[/10.247.24.189:9300]]], master [[Douglas
Ramsey][i6ypp9DSQoO3FQ6WXLwe1Q][inet[/10.247.24.189:9300]]],
cluster_name[losaq-es-cluster-afzal]} with no matching id [1]
[2012-06-27 01:38:54,052][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Ghost Maker]
[O3ISfKmaQIKdDt19x3_O9g][inet[/10.247.24.193:9300]]], master [[Ghost
Maker][O3ISfKmaQIKdDt19x3_O9g][inet[/10.247.24.193:9300]]],
cluster_name[losaq-es-cluster-afzal]} with no matching id [1]

dadoonet · June 27, 2012, 6:04am

Are your nodes on the same network ?
Did you open 9300 port on each node ?
Did you change your settings file ?

David
Twitter : @dadoonet / @elasticsearchfr

Le 27 juin 2012 à 07:54, ajan jan.afzal@gmail.com a écrit :

I have an ES cluster with 5 nodes on different SLES VM's. I keep
getting this error when I start the ES nodes and they don't form a
cluster

[2012-06-27 01:38:54,052][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Wildside][lcw2NIVjTr-
KfreUoPE0yg][inet[/10.247.24.194:9300]]{data=false}], master
[[Wildside][lcw2NIVjTr-KfreUoPE0yg][inet[/10.247.24.194:9300]]
{data=false}], cluster_name[losaq-es-cluster-afzal]} with no matching
id [1]
[2012-06-27 01:38:54,051][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Douglas Ramsey]
[i6ypp9DSQoO3FQ6WXLwe1Q][inet[/10.247.24.189:9300]]], master [[Douglas
Ramsey][i6ypp9DSQoO3FQ6WXLwe1Q][inet[/10.247.24.189:9300]]],
cluster_name[losaq-es-cluster-afzal]} with no matching id [1]
[2012-06-27 01:38:54,052][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Ghost Maker]
[O3ISfKmaQIKdDt19x3_O9g][inet[/10.247.24.193:9300]]], master [[Ghost
Maker][O3ISfKmaQIKdDt19x3_O9g][inet[/10.247.24.193:9300]]],
cluster_name[losaq-es-cluster-afzal]} with no matching id [1]

ajan · June 27, 2012, 10:18am

yes, yes and yes.

Not sure if it is a bug. This got resolved when I started the data
node first and then started other nodes. Is there a sequence that
needs to be followed?

On Jun 27, 11:04 am, David Pilato da...@pilato.fr wrote:

Are your nodes on the same network ?
Did you open 9300 port on each node ?
Did you change your settings file ?

David
Twitter : @dadoonet / @elasticsearchfr

Le 27 juin 2012 à 07:54, ajan jan.af...@gmail.com a écrit :

I have an ES cluster with 5 nodes on different SLES VM's. I keep
getting this error when I start the ES nodes and they don't form a
cluster

[2012-06-27 01:38:54,052][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Wildside][lcw2NIVjTr-
KfreUoPE0yg][inet[/10.247.24.194:9300]]{data=false}], master
[[Wildside][lcw2NIVjTr-KfreUoPE0yg][inet[/10.247.24.194:9300]]
{data=false}], cluster_name[losaq-es-cluster-afzal]} with no matching
id [1]
[2012-06-27 01:38:54,051][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Douglas Ramsey]
[i6ypp9DSQoO3FQ6WXLwe1Q][inet[/10.247.24.189:9300]]], master [[Douglas
Ramsey][i6ypp9DSQoO3FQ6WXLwe1Q][inet[/10.247.24.189:9300]]],
cluster_name[losaq-es-cluster-afzal]} with no matching id [1]
[2012-06-27 01:38:54,052][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Ghost Maker]
[O3ISfKmaQIKdDt19x3_O9g][inet[/10.247.24.193:9300]]], master [[Ghost
Maker][O3ISfKmaQIKdDt19x3_O9g][inet[/10.247.24.193:9300]]],
cluster_name[losaq-es-cluster-afzal]} with no matching id [1]

dadoonet · June 27, 2012, 10:26am

Hmmm. That means that you define one "regular" node, and others don't hold any data ?

I don't know if a "client only node" can be elected as a master.

But, yes, it's best to start your cluster (with all data nodes) before starting clients.

David
Twitter : @dadoonet / @elasticsearchfr

Le 27 juin 2012 à 12:18, ajan jan.afzal@gmail.com a écrit :

yes, yes and yes.

Not sure if it is a bug. This got resolved when I started the data
node first and then started other nodes. Is there a sequence that
needs to be followed?

On Jun 27, 11:04 am, David Pilato da...@pilato.fr wrote:

Are your nodes on the same network ?
Did you open 9300 port on each node ?
Did you change your settings file ?

David
Twitter : @dadoonet / @elasticsearchfr

Le 27 juin 2012 à 07:54, ajan jan.af...@gmail.com a écrit :

I have an ES cluster with 5 nodes on different SLES VM's. I keep
getting this error when I start the ES nodes and they don't form a
cluster

[2012-06-27 01:38:54,052][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Wildside][lcw2NIVjTr-
KfreUoPE0yg][inet[/10.247.24.194:9300]]{data=false}], master
[[Wildside][lcw2NIVjTr-KfreUoPE0yg][inet[/10.247.24.194:9300]]
{data=false}], cluster_name[losaq-es-cluster-afzal]} with no matching
id [1]
[2012-06-27 01:38:54,051][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Douglas Ramsey]
[i6ypp9DSQoO3FQ6WXLwe1Q][inet[/10.247.24.189:9300]]], master [[Douglas
Ramsey][i6ypp9DSQoO3FQ6WXLwe1Q][inet[/10.247.24.189:9300]]],
cluster_name[losaq-es-cluster-afzal]} with no matching id [1]
[2012-06-27 01:38:54,052][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Ghost Maker]
[O3ISfKmaQIKdDt19x3_O9g][inet[/10.247.24.193:9300]]], master [[Ghost
Maker][O3ISfKmaQIKdDt19x3_O9g][inet[/10.247.24.193:9300]]],
cluster_name[losaq-es-cluster-afzal]} with no matching id [1]

11110 · October 3, 2012, 1:58pm

I hope so check discovery.zen.ping.timeout in
ES_HOME/config/elasticsearch.yml

if timeout value is 3s then i propose to change about 10s

2012년 6월 27일 수요일 오후 2시 54분 51초 UTC+9, ajan 님의 말:

I have an ES cluster with 5 nodes on different SLES VM's. I keep
getting this error when I start the ES nodes and they don't form a
cluster

[2012-06-27 01:38:54,052][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Wildside][lcw2NIVjTr-
KfreUoPE0yg][inet[/10.247.24.194:9300]]{data=false}], master
[[Wildside][lcw2NIVjTr-KfreUoPE0yg][inet[/10.247.24.194:9300]]
{data=false}], cluster_name[losaq-es-cluster-afzal]} with no matching
id [1]
[2012-06-27 01:38:54,051][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Douglas Ramsey]
[i6ypp9DSQoO3FQ6WXLwe1Q][inet[/10.247.24.189:9300]]], master [[Douglas
Ramsey][i6ypp9DSQoO3FQ6WXLwe1Q][inet[/10.247.24.189:9300]]],
cluster_name[losaq-es-cluster-afzal]} with no matching id [1]
[2012-06-27 01:38:54,052][WARN ][discovery.zen.ping.multicast] [Nikki]
received ping response ping_response{target [[Ghost Maker]
[O3ISfKmaQIKdDt19x3_O9g][inet[/10.247.24.193:9300]]], master [[Ghost
Maker][O3ISfKmaQIKdDt19x3_O9g][inet[/10.247.24.193:9300]]],
cluster_name[losaq-es-cluster-afzal]} with no matching id [1]

--

Topic		Replies	Views
Node is not joining the cluster (ES-5.6.3) Elasticsearch	7	1924	December 14, 2017
Elastic search node not forming cluster, running on windows server 2012 VM on windows Azure Elasticsearch	3	1167	July 5, 2017
Node not joining Elasticsearch cluster Elasticsearch	9	606	June 9, 2021
Nodes not joining my cluster Elasticsearch	3	349	August 1, 2019
Not able to create a cluster with ES 5.6? Elasticsearch	9	4804	October 17, 2017

Nodes not joining cluster

Related topics