I am a beginner on Elasticsearch.
I have Logstash/Elasticsearch/Kibana running in HP Cloud.
This is the master node.
I tried to have at least another node (also in HP Cloud) to set up an
Elasticsearch cluster.
However, I found the non-master node still doesn’t join the intended
cluster.
My setup is the following:
Master Node
elasticsearch 0.90.3
logstash 1.2.2
kibana 3.0.0milestone4
In /etc/elasticsearch/elasticsearch.yml:
cluster.name: ls_cluster
node.name: logstash1
I also tried changing the following on the non-master node, but it didn’t
make any difference.
node.master: false
node.data: true
transport.tcp.port: 9301
http.port: 9201
The same result with using elasticsearch 0.90.9 & logstash 1.3.3.
On 1 February 2014 10:39, Indra Suryanata insury@gmail.com wrote:
I am a beginner on Elasticsearch.
I have Logstash/Elasticsearch/Kibana running in HP Cloud.
This is the master node.
I tried to have at least another node (also in HP Cloud) to set up an
Elasticsearch cluster.
However, I found the non-master node still doesn't join the intended
cluster.
My setup is the following:
Master Node
elasticsearch 0.90.3
logstash 1.2.2
kibana 3.0.0milestone4
In /etc/elasticsearch/elasticsearch.yml:
cluster.name: ls_cluster
node.name: logstash1
I also tried changing the following on the non-master node, but it didn't
make any difference.
node.master: false
node.data: true
transport.tcp.port: 9301
http.port: 9201
The same result with using elasticsearch 0.90.9 & logstash 1.3.3.
On 1 February 2014 10:39, Indra Suryanata <ins...@gmail.com <javascript:>>wrote:
I am a beginner on Elasticsearch.
I have Logstash/Elasticsearch/Kibana running in HP Cloud.
This is the master node.
I tried to have at least another node (also in HP Cloud) to set up an
Elasticsearch cluster.
However, I found the non-master node still doesn’t join the intended
cluster.
My setup is the following:
Master Node
elasticsearch 0.90.3
logstash 1.2.2
kibana 3.0.0milestone4
In /etc/elasticsearch/elasticsearch.yml:
cluster.name: ls_cluster
node.name: logstash1
I also tried changing the following on the non-master node, but it didn’t
make any difference.
node.master: false
node.data: true
transport.tcp.port: 9301
http.port: 9201
The same result with using elasticsearch 0.90.9 & logstash 1.3.3.
network.host is the IP that the node itself will listen on when advertising
the service, so if you set that to the master node IP then each node will
try and listen on that same IP. Which is not what you want.
You want to set;
discovery.zen.ping.unicast: $IP_OF_MASTER
On 1 February 2014 10:39, Indra Suryanata ins...@gmail.com wrote:
I am a beginner on Elasticsearch.
I have Logstash/Elasticsearch/Kibana running in HP Cloud.
This is the master node.
I tried to have at least another node (also in HP Cloud) to set up an
Elasticsearch cluster.
However, I found the non-master node still doesn't join the intended
cluster.
My setup is the following:
Master Node
elasticsearch 0.90.3
logstash 1.2.2
kibana 3.0.0milestone4
In /etc/elasticsearch/elasticsearch.yml:
cluster.name: ls_cluster
node.name: logstash1
I also tried changing the following on the non-master node, but it
didn't make any difference.
node.master: false
node.data: true
transport.tcp.port: 9301
http.port: 9201
The same result with using elasticsearch 0.90.9 & logstash 1.3.3.
Thanks Mark, it works! - Really appreciate your help.
As you suggested, I set
discovery.zen.ping.unicast.hosts: $IP_OF_MASTER
in elasticsearch.yml of the Non-Master Node.
Regards,
Indra
On Friday, January 31, 2014 4:08:19 PM UTC-8, Mark Walkom wrote:
network.host is the IP that the node itself will listen on when
advertising the service, so if you set that to the master node IP then each
node will try and listen on that same IP. Which is not what you want.
You want to set;
discovery.zen.ping.unicast: $IP_OF_MASTER
On 1 February 2014 10:39, Indra Suryanata ins...@gmail.com wrote:
I am a beginner on Elasticsearch.
I have Logstash/Elasticsearch/Kibana running in HP Cloud.
This is the master node.
I tried to have at least another node (also in HP Cloud) to set up an
Elasticsearch cluster.
However, I found the non-master node still doesn’t join the intended
cluster.
My setup is the following:
Master Node
elasticsearch 0.90.3
logstash 1.2.2
kibana 3.0.0milestone4
In /etc/elasticsearch/elasticsearch.yml:
cluster.name: ls_cluster
node.name: logstash1
I also tried changing the following on the non-master node, but it
didn’t make any difference.
node.master: false
node.data: true
transport.tcp.port: 9301
http.port: 9201
The same result with using elasticsearch 0.90.9 & logstash 1.3.3.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.