# Elasticsearch Cluster: How to ensure node communication

**URL:** <https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448>\
**Category:** Elasticsearch\
**Created:** [July 18, 2018, 5:52am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448 "2018-07-18T05:52:42Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [July 18, 2018, 5:52am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/1 "2018-07-18T05:52:42Z")

</div>

Hello

Please have a look at ES configuration and let me know what's wrong

```
Node:1

     node.name: "es-node-1"
     
    node.master: true
     
    node.data: true
     
    network.host: 10.0.0.74
    http.port: 9200
     
    discovery.zen.ping.unicast.hosts: ["10.0.0.30","10.0.0.74"]

Node 2:

    node.name: "es-node-2"
     
    node.master: true
     
    node.data: true
     
    network.host: 10.0.0.30
    http.port: 9200
     
    discovery.zen.ping.unicast.hosts: ["10.0.0.30","10.0.0.74"]

```

When I hit: ([http://10.0.0.30:9200/\_cluster/health/?level=shards?pretty](http://10.0.0.30:9200/_cluster/health/?level=shards?pretty))

response:

`{"cluster_name":"my-cluster","status":"yellow","timed_out":false,"number_of_nodes":1,"number_of_data_nodes":1,"active_primary_shards":1,"active_shards":1,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":1,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":0,"active_shards_percent_as_number":50.0}`

number of nodes is showing 1 instead of 2.

did I miss anything in config file?

Rahul

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [July 18, 2018, 5:56am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/2 "2018-07-18T05:56:13Z")

</div>

Those config file do not contain cluster names, but I can see from your Rest response that your `10.0.0.30` node (Node 2) thinks its cluster name is "my-cluster".

What is the full configuration that you are using for these nodes?

---

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [July 18, 2018, 6:02am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/3 "2018-07-18T06:02:03Z")

</div>

Hey @TimV

this is my full configuration

```
bootstrap.memory_lock: true
cluster.name: my-cluster
 
node.name: "es-node-1"
 
node.master: true
 
node.data: true
 
network.host: 10.0.0.74
http.port: 9200
 
discovery.zen.ping.unicast.hosts: ["10.0.0.30:9200","10.0.0.74"]
thread_pool.bulk.queue_size: 2000
path.data: C:\ProgramData\Elastic\Elasticsearch\data
path.logs: C:\ProgramData\Elastic\Elasticsearch\logs
```

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [July 18, 2018, 6:05am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/4 "2018-07-18T06:05:55Z")

</div>

What about the other node?

---

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [July 18, 2018, 6:28am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/5 "2018-07-18T06:28:47Z")

</div>

@TimV

please have a look

```
bootstrap.memory_lock: true
cluster.name: my-cluster
 
node.name: "es-node-2"
 
node.master: true
 
node.data: true
 
network.host: 10.0.0.30
http.port: 9200
 
discovery.zen.ping.unicast.hosts: ["10.0.0.30","10.0.0.74:9200"]
thread_pool.bulk.queue_size: 2000
path.data: C:\ProgramData\Elastic\Elasticsearch\data
path.logs: C:\ProgramData\Elastic\Elasticsearch\logs
```

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [July 18, 2018, 6:32am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/6 "2018-07-18T06:32:08Z")

</div>

You've specified port `9200` in the ping hosts. That is the HTTP port, but Zen uses the transport port (`9300`) for discovery.

---

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [July 18, 2018, 6:35am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/7 "2018-07-18T06:35:09Z")

</div>

should I modify to

discovery.zen.ping.unicast.hosts: ["10.0.0.30","10.0.0.74"]  
transport.tcp.port: 9300

---

<div class="post-metadata">

**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\
**Post date:** [July 18, 2018, 7:52am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/8 "2018-07-18T07:52:08Z")

</div>

> [@rahulnama](#):
>
> ["10.0.0.30","10.0.0.74:9200"]

use ip not 9200  
change to ["10.0.0.30","10.0.0.74"] and try

---

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [July 18, 2018, 8:13am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/9 "2018-07-18T08:13:02Z")

</div>

Hey @zqc0512

I've tried but no use. ☹

by any chance, do you think existing data is causing the problem?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 18, 2018, 8:15am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/10 "2018-07-18T08:15:41Z")

</div>

If you have 2 master eligible nodes, you should set `minimum_master_nodes` to `2` as well according to [these guidelines](https://www.elastic.co/guide/en/elasticsearch/reference/6.3/modules-node.html#split-brain).

> [@rahulnama](#):
>
> thread\_pool.bulk.queue\_size: 2000

Why are you setting this so high?

---

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [July 18, 2018, 8:28am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/11 "2018-07-18T08:28:56Z")

</div>

@Christian_Dahlqvist

I will set to 2 and give it a try.

regarding queue size, I've got bulk rejection exception, so I increased it.

Any dis-advantage If we keep it so high?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 18, 2018, 8:31am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/12 "2018-07-18T08:31:56Z")

</div>

Read [this blog post on the topic](https://www.elastic.co/blog/why-am-i-seeing-bulk-rejections-in-my-elasticsearch-cluster). Increasing this parameter that much will add additional memory pressure without necessarily increasing throughput. How many indices/shards are you actively indexing into?

---

<div class="post-metadata">

**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\
**Post date:** [July 18, 2018, 8:35am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/13 "2018-07-18T08:35:42Z")

</div>

> [@rahulnama](#):
>
> "unassigned\_shards":1,

you have two data node, one index have 2 replica?

---

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [July 18, 2018, 8:35am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/14 "2018-07-18T08:35:53Z")

</div>

@Christian_Dahlqvist

You can see it here

`{"cluster_name":"my-cluster","status":"yellow","timed_out":false,"number_of_nodes":1,"number_of_data_nodes":1,"active_primary_shards":114,"active_shards":114,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":107,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":0,"active_shards_percent_as_number":51.58371040723983}`

Also, If possible please let me know, having these many shards is a good practise or not?

by the way, thanks for the blog post

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 18, 2018, 8:45am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/15 "2018-07-18T08:45:48Z")

</div>

Read [this blog post](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster) for guidance on shards and sharding.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 15, 2018, 8:45am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-how-to-ensure-node-communication/140448/16 "2018-08-15T08:45:54Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
