# Anyone have issues with node communication in a cluster?

**URL:** <https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149>\
**Category:** Elasticsearch\
**Created:** [July 25, 2010, 5:08pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149 "2010-07-25T17:08:37Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![Samuel\_Doyle](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@Samuel\_Doyle](https://discuss.elastic.co/u/Samuel_Doyle)\
**Post date:** [July 25, 2010, 5:08pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/1 "2010-07-25T17:08:37Z")

</div>

I am testing in a staging environment with several servers but have unable  
to successfully get elastic search to recognize each peer.  
Multicast is enabled and being used by other parts of our application. I  
have also tried going the unicast route with elastic search after disabling  
multicast with no luck.

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [July 25, 2010, 6:52pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/2 "2010-07-25T18:52:29Z")

</div>

Can you post your unicast configuration? In general, you can  
set discovery.zen to TRACE to see whats going on...

On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com) wrote:

> I am testing in a staging environment with several servers but have unable  
> to successfully get Elasticsearch to recognize each peer.  
> Multicast is enabled and being used by other parts of our application. I  
> have also tried going the unicast route with Elasticsearch after disabling  
> multicast with no luck.

---

<div class="post-metadata">

**Author:** ![Samuel\_Doyle](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@Samuel\_Doyle](https://discuss.elastic.co/u/Samuel_Doyle)\
**Post date:** [July 25, 2010, 7:06pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/3 "2010-07-25T19:06:45Z")

</div>

Ah great, I'll give that a shot to see if I can get some more info.

Thanks

Here is a current config, I've been trying various versions.

name: stage01

cluster:  
name: esstagetest

node:  
data: true

http:  
enabled: true

gateway:  
type: fs  
fs:  
location: /home/esearch/gateway/indices

index :  
gateawy:  
snapshot\_interval: 30s  
number\_of\_shards : 5  
number\_of\_replicas : 4  
analysis :  
analyzer :  
standard :  
type : standard

store:  
type: memory  
memory:  
cache\_size: 100m  
buffer\_size: 10k

#discovery:

# zen:

# ping:

# multicast:

# enabled: false

# unicast:

# hosts: ["stage01:9301", "stage02:9302"]

transport:  
tcp:  
port: 9300

path:  
logs: /home/esearch/gateway/logs/stage01

On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon  
[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:

> Can you post your unicast configuration? In general, you can  
> set discovery.zen to TRACE to see whats going on...
> 
> On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> 
> > I am testing in a staging environment with several servers but have unable  
> > to successfully get Elasticsearch to recognize each peer.  
> > Multicast is enabled and being used by other parts of our application. I  
> > have also tried going the unicast route with Elasticsearch after disabling  
> > multicast with no luck.

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [July 25, 2010, 7:32pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/4 "2010-07-25T19:32:58Z")

</div>

Can you try and replace stage01 and stage02 with the actual IPs, maybe they  
are not resolved properly?

On Sun, Jul 25, 2010 at 10:06 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:

> Ah great, I'll give that a shot to see if I can get some more info.
> 
> Thanks
> 
> Here is a current config, I've been trying various versions.
> 
> name: stage01
> 
> cluster:  
> name: esstagetest
> 
> node:  
> data: true
> 
> http:  
> enabled: true
> 
> gateway:  
> type: fs  
> fs:  
> location: /home/esearch/gateway/indices
> 
> index :  
> gateawy:  
> snapshot\_interval: 30s  
> number\_of\_shards : 5  
> number\_of\_replicas : 4  
> analysis :  
> analyzer :  
> standard :  
> type : standard
> 
> store:  
> type: memory  
> memory:  
> cache\_size: 100m  
> buffer\_size: 10k
> 
> #discovery:
> 
> # zen:
> 
> # ping:
> 
> # multicast:
> 
> # enabled: false
> 
> # unicast:
> 
> # hosts: ["stage01:9301", "stage02:9302"]
> 
> transport:  
> tcp:  
> port: 9300
> 
> path:  
> logs: /home/esearch/gateway/logs/stage01
> 
> On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon \<[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)
> 
> > wrote:
> 
> > Can you post your unicast configuration? In general, you can  
> > set discovery.zen to TRACE to see whats going on...
> > 
> > On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > 
> > > I am testing in a staging environment with several servers but have  
> > > unable to successfully get Elasticsearch to recognize each peer.  
> > > Multicast is enabled and being used by other parts of our application. I  
> > > have also tried going the unicast route with Elasticsearch after disabling  
> > > multicast with no luck.

---

<div class="post-metadata">

**Author:** ![Samuel\_Doyle](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@Samuel\_Doyle](https://discuss.elastic.co/u/Samuel_Doyle)\
**Post date:** [July 25, 2010, 9:38pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/5 "2010-07-25T21:38:11Z")

</div>

Yeah I tried that as well, no luck.

On Sun, Jul 25, 2010 at 12:32 PM, Shay Banon  
[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:

> Can you try and replace stage01 and stage02 with the actual IPs, maybe they  
> are not resolved properly?
> 
> On Sun, Jul 25, 2010 at 10:06 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> 
> > Ah great, I'll give that a shot to see if I can get some more info.
> > 
> > Thanks
> > 
> > Here is a current config, I've been trying various versions.
> > 
> > name: stage01
> > 
> > cluster:  
> > name: esstagetest
> > 
> > node:  
> > data: true
> > 
> > http:  
> > enabled: true
> > 
> > gateway:  
> > type: fs  
> > fs:  
> > location: /home/esearch/gateway/indices
> > 
> > index :  
> > gateawy:  
> > snapshot\_interval: 30s  
> > number\_of\_shards : 5  
> > number\_of\_replicas : 4  
> > analysis :  
> > analyzer :  
> > standard :  
> > type : standard
> > 
> > store:  
> > type: memory  
> > memory:  
> > cache\_size: 100m  
> > buffer\_size: 10k
> > 
> > #discovery:
> > 
> > # zen:
> > 
> > # ping:
> > 
> > # multicast:
> > 
> > # enabled: false
> > 
> > # unicast:
> > 
> > # hosts: ["stage01:9301", "stage02:9302"]
> > 
> > transport:  
> > tcp:  
> > port: 9300
> > 
> > path:  
> > logs: /home/esearch/gateway/logs/stage01
> > 
> > On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon \<  
> > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > 
> > > Can you post your unicast configuration? In general, you can  
> > > set discovery.zen to TRACE to see whats going on...
> > > 
> > > On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > 
> > > > I am testing in a staging environment with several servers but have  
> > > > unable to successfully get Elasticsearch to recognize each peer.  
> > > > Multicast is enabled and being used by other parts of our application. I  
> > > > have also tried going the unicast route with Elasticsearch after disabling  
> > > > multicast with no luck.

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [July 25, 2010, 9:40pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/6 "2010-07-25T21:40:34Z")

</div>

Just saw that (I assume) the configuration you set for stage01 is to start  
on port 9300, yet you configure it in the unicast hosts with port 9301. Is  
that intentional?

-shay.banon

On Mon, Jul 26, 2010 at 12:38 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:

> Yeah I tried that as well, no luck.
> 
> On Sun, Jul 25, 2010 at 12:32 PM, Shay Banon \<[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)
> 
> > wrote:
> 
> > Can you try and replace stage01 and stage02 with the actual IPs, maybe  
> > they are not resolved properly?
> > 
> > On Sun, Jul 25, 2010 at 10:06 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > 
> > > Ah great, I'll give that a shot to see if I can get some more info.
> > > 
> > > Thanks
> > > 
> > > Here is a current config, I've been trying various versions.
> > > 
> > > name: stage01
> > > 
> > > cluster:  
> > > name: esstagetest
> > > 
> > > node:  
> > > data: true
> > > 
> > > http:  
> > > enabled: true
> > > 
> > > gateway:  
> > > type: fs  
> > > fs:  
> > > location: /home/esearch/gateway/indices
> > > 
> > > index :  
> > > gateawy:  
> > > snapshot\_interval: 30s  
> > > number\_of\_shards : 5  
> > > number\_of\_replicas : 4  
> > > analysis :  
> > > analyzer :  
> > > standard :  
> > > type : standard
> > > 
> > > store:  
> > > type: memory  
> > > memory:  
> > > cache\_size: 100m  
> > > buffer\_size: 10k
> > > 
> > > #discovery:
> > > 
> > > # zen:
> > > 
> > > # ping:
> > > 
> > > # multicast:
> > > 
> > > # enabled: false
> > > 
> > > # unicast:
> > > 
> > > # hosts: ["stage01:9301", "stage02:9302"]
> > > 
> > > transport:  
> > > tcp:  
> > > port: 9300
> > > 
> > > path:  
> > > logs: /home/esearch/gateway/logs/stage01
> > > 
> > > On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon \<  
> > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > 
> > > > Can you post your unicast configuration? In general, you can  
> > > > set discovery.zen to TRACE to see whats going on...
> > > > 
> > > > On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > > 
> > > > > I am testing in a staging environment with several servers but have  
> > > > > unable to successfully get Elasticsearch to recognize each peer.  
> > > > > Multicast is enabled and being used by other parts of our application.  
> > > > > I have also tried going the unicast route with Elasticsearch after  
> > > > > disabling multicast with no luck.

---

<div class="post-metadata">

**Author:** ![Samuel\_Doyle](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@Samuel\_Doyle](https://discuss.elastic.co/u/Samuel_Doyle)\
**Post date:** [July 25, 2010, 9:50pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/7 "2010-07-25T21:50:40Z")

</div>

I had tried various configurations this is just the latest, I tried 9300 as  
well wasn't sure about that.

On Sun, Jul 25, 2010 at 2:40 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:

> Just saw that (I assume) the configuration you set for stage01 is to start  
> on port 9300, yet you configure it in the unicast hosts with port 9301. Is  
> that intentional?
> 
> -shay.banon
> 
> On Mon, Jul 26, 2010 at 12:38 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> 
> > Yeah I tried that as well, no luck.
> > 
> > On Sun, Jul 25, 2010 at 12:32 PM, Shay Banon \<  
> > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > 
> > > Can you try and replace stage01 and stage02 with the actual IPs, maybe  
> > > they are not resolved properly?
> > > 
> > > On Sun, Jul 25, 2010 at 10:06 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > 
> > > > Ah great, I'll give that a shot to see if I can get some more info.
> > > > 
> > > > Thanks
> > > > 
> > > > Here is a current config, I've been trying various versions.
> > > > 
> > > > name: stage01
> > > > 
> > > > cluster:  
> > > > name: esstagetest
> > > > 
> > > > node:  
> > > > data: true
> > > > 
> > > > http:  
> > > > enabled: true
> > > > 
> > > > gateway:  
> > > > type: fs  
> > > > fs:  
> > > > location: /home/esearch/gateway/indices
> > > > 
> > > > index :  
> > > > gateawy:  
> > > > snapshot\_interval: 30s  
> > > > number\_of\_shards : 5  
> > > > number\_of\_replicas : 4  
> > > > analysis :  
> > > > analyzer :  
> > > > standard :  
> > > > type : standard
> > > > 
> > > > store:  
> > > > type: memory  
> > > > memory:  
> > > > cache\_size: 100m  
> > > > buffer\_size: 10k
> > > > 
> > > > #discovery:
> > > > 
> > > > # zen:
> > > > 
> > > > # ping:
> > > > 
> > > > # multicast:
> > > > 
> > > > # enabled: false
> > > > 
> > > > # unicast:
> > > > 
> > > > # hosts: ["stage01:9301", "stage02:9302"]
> > > > 
> > > > transport:  
> > > > tcp:  
> > > > port: 9300
> > > > 
> > > > path:  
> > > > logs: /home/esearch/gateway/logs/stage01
> > > > 
> > > > On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon \<  
> > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > 
> > > > > Can you post your unicast configuration? In general, you can  
> > > > > set discovery.zen to TRACE to see whats going on...
> > > > > 
> > > > > On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > > > 
> > > > > > I am testing in a staging environment with several servers but have  
> > > > > > unable to successfully get Elasticsearch to recognize each peer.  
> > > > > > Multicast is enabled and being used by other parts of our application.  
> > > > > > I have also tried going the unicast route with Elasticsearch after  
> > > > > > disabling multicast with no luck.

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [July 25, 2010, 10:02pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/8 "2010-07-25T22:02:50Z")

</div>

Basically, when you start a node, you see the transport module prints the  
publish address it uses, this address should be used in the hosts list.

-shay.banon

On Mon, Jul 26, 2010 at 12:50 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:

> I had tried various configurations this is just the latest, I tried 9300 as  
> well wasn't sure about that.
> 
> On Sun, Jul 25, 2010 at 2:40 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:
> 
> > Just saw that (I assume) the configuration you set for stage01 is to start  
> > on port 9300, yet you configure it in the unicast hosts with port 9301. Is  
> > that intentional?
> > 
> > -shay.banon
> > 
> > On Mon, Jul 26, 2010 at 12:38 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > 
> > > Yeah I tried that as well, no luck.
> > > 
> > > On Sun, Jul 25, 2010 at 12:32 PM, Shay Banon \<  
> > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > 
> > > > Can you try and replace stage01 and stage02 with the actual IPs, maybe  
> > > > they are not resolved properly?
> > > > 
> > > > On Sun, Jul 25, 2010 at 10:06 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > > 
> > > > > Ah great, I'll give that a shot to see if I can get some more info.
> > > > > 
> > > > > Thanks
> > > > > 
> > > > > Here is a current config, I've been trying various versions.
> > > > > 
> > > > > name: stage01
> > > > > 
> > > > > cluster:  
> > > > > name: esstagetest
> > > > > 
> > > > > node:  
> > > > > data: true
> > > > > 
> > > > > http:  
> > > > > enabled: true
> > > > > 
> > > > > gateway:  
> > > > > type: fs  
> > > > > fs:  
> > > > > location: /home/esearch/gateway/indices
> > > > > 
> > > > > index :  
> > > > > gateawy:  
> > > > > snapshot\_interval: 30s  
> > > > > number\_of\_shards : 5  
> > > > > number\_of\_replicas : 4  
> > > > > analysis :  
> > > > > analyzer :  
> > > > > standard :  
> > > > > type : standard
> > > > > 
> > > > > store:  
> > > > > type: memory  
> > > > > memory:  
> > > > > cache\_size: 100m  
> > > > > buffer\_size: 10k
> > > > > 
> > > > > #discovery:
> > > > > 
> > > > > # zen:
> > > > > 
> > > > > # ping:
> > > > > 
> > > > > # multicast:
> > > > > 
> > > > > # enabled: false
> > > > > 
> > > > > # unicast:
> > > > > 
> > > > > # hosts: ["stage01:9301", "stage02:9302"]
> > > > > 
> > > > > transport:  
> > > > > tcp:  
> > > > > port: 9300
> > > > > 
> > > > > path:  
> > > > > logs: /home/esearch/gateway/logs/stage01
> > > > > 
> > > > > On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon \<  
> > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > 
> > > > > > Can you post your unicast configuration? In general, you can  
> > > > > > set discovery.zen to TRACE to see whats going on...
> > > > > > 
> > > > > > On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > > > > 
> > > > > > > I am testing in a staging environment with several servers but have  
> > > > > > > unable to successfully get Elasticsearch to recognize each peer.  
> > > > > > > Multicast is enabled and being used by other parts of our  
> > > > > > > application. I have also tried going the unicast route with Elasticsearch  
> > > > > > > after disabling multicast with no luck.

---

<div class="post-metadata">

**Author:** ![Samuel\_Doyle](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@Samuel\_Doyle](https://discuss.elastic.co/u/Samuel_Doyle)\
**Post date:** [July 25, 2010, 11:38pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/9 "2010-07-25T23:38:02Z")

</div>

How do I control which port it publishes to, it doesn't appear I have any  
control over that.

Thanks

On Sun, Jul 25, 2010 at 3:02 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:

> Basically, when you start a node, you see the transport module prints the  
> publish address it uses, this address should be used in the hosts list.
> 
> -shay.banon
> 
> On Mon, Jul 26, 2010 at 12:50 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> 
> > I had tried various configurations this is just the latest, I tried 9300  
> > as well wasn't sure about that.
> > 
> > On Sun, Jul 25, 2010 at 2:40 PM, Shay Banon \<[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)
> > 
> > > wrote:
> > 
> > > Just saw that (I assume) the configuration you set for stage01 is to  
> > > start on port 9300, yet you configure it in the unicast hosts with port  
> > > 9301. Is that intentional?
> > > 
> > > -shay.banon
> > > 
> > > On Mon, Jul 26, 2010 at 12:38 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > 
> > > > Yeah I tried that as well, no luck.
> > > > 
> > > > On Sun, Jul 25, 2010 at 12:32 PM, Shay Banon \<  
> > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > 
> > > > > Can you try and replace stage01 and stage02 with the actual IPs, maybe  
> > > > > they are not resolved properly?
> > > > > 
> > > > > On Sun, Jul 25, 2010 at 10:06 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > > > 
> > > > > > Ah great, I'll give that a shot to see if I can get some more info.
> > > > > > 
> > > > > > Thanks
> > > > > > 
> > > > > > Here is a current config, I've been trying various versions.
> > > > > > 
> > > > > > name: stage01
> > > > > > 
> > > > > > cluster:  
> > > > > > name: esstagetest
> > > > > > 
> > > > > > node:  
> > > > > > data: true
> > > > > > 
> > > > > > http:  
> > > > > > enabled: true
> > > > > > 
> > > > > > gateway:  
> > > > > > type: fs  
> > > > > > fs:  
> > > > > > location: /home/esearch/gateway/indices
> > > > > > 
> > > > > > index :  
> > > > > > gateawy:  
> > > > > > snapshot\_interval: 30s  
> > > > > > number\_of\_shards : 5  
> > > > > > number\_of\_replicas : 4  
> > > > > > analysis :  
> > > > > > analyzer :  
> > > > > > standard :  
> > > > > > type : standard
> > > > > > 
> > > > > > store:  
> > > > > > type: memory  
> > > > > > memory:  
> > > > > > cache\_size: 100m  
> > > > > > buffer\_size: 10k
> > > > > > 
> > > > > > #discovery:
> > > > > > 
> > > > > > # zen:
> > > > > > 
> > > > > > # ping:
> > > > > > 
> > > > > > # multicast:
> > > > > > 
> > > > > > # enabled: false
> > > > > > 
> > > > > > # unicast:
> > > > > > 
> > > > > > # hosts: ["stage01:9301", "stage02:9302"]
> > > > > > 
> > > > > > transport:  
> > > > > > tcp:  
> > > > > > port: 9300
> > > > > > 
> > > > > > path:  
> > > > > > logs: /home/esearch/gateway/logs/stage01
> > > > > > 
> > > > > > On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon \<  
> > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > 
> > > > > > > Can you post your unicast configuration? In general, you can  
> > > > > > > set discovery.zen to TRACE to see whats going on...
> > > > > > > 
> > > > > > > On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle \<[samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)
> > > > > > > 
> > > > > > > > wrote:
> > > > > > > 
> > > > > > > > I am testing in a staging environment with several servers but have  
> > > > > > > > unable to successfully get Elasticsearch to recognize each peer.  
> > > > > > > > Multicast is enabled and being used by other parts of our  
> > > > > > > > application. I have also tried going the unicast route with Elasticsearch  
> > > > > > > > after disabling multicast with no luck.

---

<div class="post-metadata">

**Author:** ![Samuel\_Doyle](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@Samuel\_Doyle](https://discuss.elastic.co/u/Samuel_Doyle)\
**Post date:** [July 25, 2010, 11:46pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/10 "2010-07-25T23:46:59Z")

</div>

If I specify a network: [some ip address] it then publishes on another  
differently nic:

[18:44:09,586][INFO][http] [stage01] bound\_address  
{inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/192.168.122.1:9200]}  
[18:44:09,795][INFO][jmx] [stage01] bound\_address  
{service:jmx:rmi:///jndi/rmi://:9400/jmxrmi}, publish\_address  
{service:jmx:rmi:///jndi/rmi://192.168.122.1:9400/jmxrmi}

That is not the ip or nic I specify

On Sun, Jul 25, 2010 at 4:38 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com) wrote:

> How do I control which port it publishes to, it doesn't appear I have any  
> control over that.
> 
> Thanks
> 
> On Sun, Jul 25, 2010 at 3:02 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:
> 
> > Basically, when you start a node, you see the transport module prints the  
> > publish address it uses, this address should be used in the hosts list.
> > 
> > -shay.banon
> > 
> > On Mon, Jul 26, 2010 at 12:50 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > 
> > > I had tried various configurations this is just the latest, I tried 9300  
> > > as well wasn't sure about that.
> > > 
> > > On Sun, Jul 25, 2010 at 2:40 PM, Shay Banon \<  
> > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > 
> > > > Just saw that (I assume) the configuration you set for stage01 is to  
> > > > start on port 9300, yet you configure it in the unicast hosts with port  
> > > > 9301. Is that intentional?
> > > > 
> > > > -shay.banon
> > > > 
> > > > On Mon, Jul 26, 2010 at 12:38 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > > 
> > > > > Yeah I tried that as well, no luck.
> > > > > 
> > > > > On Sun, Jul 25, 2010 at 12:32 PM, Shay Banon \<  
> > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > 
> > > > > > Can you try and replace stage01 and stage02 with the actual IPs, maybe  
> > > > > > they are not resolved properly?
> > > > > > 
> > > > > > On Sun, Jul 25, 2010 at 10:06 PM, Samuel Doyle \<[samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)
> > > > > > 
> > > > > > > wrote:
> > > > > > 
> > > > > > > Ah great, I'll give that a shot to see if I can get some more info.
> > > > > > > 
> > > > > > > Thanks
> > > > > > > 
> > > > > > > Here is a current config, I've been trying various versions.
> > > > > > > 
> > > > > > > name: stage01
> > > > > > > 
> > > > > > > cluster:  
> > > > > > > name: esstagetest
> > > > > > > 
> > > > > > > node:  
> > > > > > > data: true
> > > > > > > 
> > > > > > > http:  
> > > > > > > enabled: true
> > > > > > > 
> > > > > > > gateway:  
> > > > > > > type: fs  
> > > > > > > fs:  
> > > > > > > location: /home/esearch/gateway/indices
> > > > > > > 
> > > > > > > index :  
> > > > > > > gateawy:  
> > > > > > > snapshot\_interval: 30s  
> > > > > > > number\_of\_shards : 5  
> > > > > > > number\_of\_replicas : 4  
> > > > > > > analysis :  
> > > > > > > analyzer :  
> > > > > > > standard :  
> > > > > > > type : standard
> > > > > > > 
> > > > > > > store:  
> > > > > > > type: memory  
> > > > > > > memory:  
> > > > > > > cache\_size: 100m  
> > > > > > > buffer\_size: 10k
> > > > > > > 
> > > > > > > #discovery:
> > > > > > > 
> > > > > > > # zen:
> > > > > > > 
> > > > > > > # ping:
> > > > > > > 
> > > > > > > # multicast:
> > > > > > > 
> > > > > > > # enabled: false
> > > > > > > 
> > > > > > > # unicast:
> > > > > > > 
> > > > > > > # hosts: ["stage01:9301", "stage02:9302"]
> > > > > > > 
> > > > > > > transport:  
> > > > > > > tcp:  
> > > > > > > port: 9300
> > > > > > > 
> > > > > > > path:  
> > > > > > > logs: /home/esearch/gateway/logs/stage01
> > > > > > > 
> > > > > > > On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon \<  
> > > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > > 
> > > > > > > > Can you post your unicast configuration? In general, you can  
> > > > > > > > set discovery.zen to TRACE to see whats going on...
> > > > > > > > 
> > > > > > > > On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle \<  
> > > > > > > > [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)\> wrote:
> > > > > > > > 
> > > > > > > > > I am testing in a staging environment with several servers but have  
> > > > > > > > > unable to successfully get Elasticsearch to recognize each peer.  
> > > > > > > > > Multicast is enabled and being used by other parts of our  
> > > > > > > > > application. I have also tried going the unicast route with Elasticsearch  
> > > > > > > > > after disabling multicast with no luck.

---

<div class="post-metadata">

**Author:** ![Samuel\_Doyle](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@Samuel\_Doyle](https://discuss.elastic.co/u/Samuel_Doyle)\
**Post date:** [July 25, 2010, 11:59pm UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/11 "2010-07-25T23:59:25Z")

</div>

I've also tried setting the address for multicast seems I have no control  
over what it does.

On Sun, Jul 25, 2010 at 4:46 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com) wrote:

> If I specify a network: [some ip address] it then publishes on another  
> differently nic:
> 
> [18:44:09,586][INFO][http] [stage01] bound\_address  
> {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/192.168.122.1:9200]}  
> [18:44:09,795][INFO][jmx] [stage01] bound\_address  
> {service:jmx:rmi:///jndi/rmi://:9400/jmxrmi}, publish\_address  
> {service:jmx:rmi:///jndi/rmi://192.168.122.1:9400/jmxrmi}
> 
> That is not the ip or nic I specify
> 
> On Sun, Jul 25, 2010 at 4:38 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> 
> > How do I control which port it publishes to, it doesn't appear I have any  
> > control over that.
> > 
> > Thanks
> > 
> > On Sun, Jul 25, 2010 at 3:02 PM, Shay Banon \<[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)
> > 
> > > wrote:
> > 
> > > Basically, when you start a node, you see the transport module prints the  
> > > publish address it uses, this address should be used in the hosts list.
> > > 
> > > -shay.banon
> > > 
> > > On Mon, Jul 26, 2010 at 12:50 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > 
> > > > I had tried various configurations this is just the latest, I tried 9300  
> > > > as well wasn't sure about that.
> > > > 
> > > > On Sun, Jul 25, 2010 at 2:40 PM, Shay Banon \<  
> > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > 
> > > > > Just saw that (I assume) the configuration you set for stage01 is to  
> > > > > start on port 9300, yet you configure it in the unicast hosts with port  
> > > > > 9301. Is that intentional?
> > > > > 
> > > > > -shay.banon
> > > > > 
> > > > > On Mon, Jul 26, 2010 at 12:38 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > > > 
> > > > > > Yeah I tried that as well, no luck.
> > > > > > 
> > > > > > On Sun, Jul 25, 2010 at 12:32 PM, Shay Banon \<  
> > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > 
> > > > > > > Can you try and replace stage01 and stage02 with the actual IPs,  
> > > > > > > maybe they are not resolved properly?
> > > > > > > 
> > > > > > > On Sun, Jul 25, 2010 at 10:06 PM, Samuel Doyle \<  
> > > > > > > [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)\> wrote:
> > > > > > > 
> > > > > > > > Ah great, I'll give that a shot to see if I can get some more info.
> > > > > > > > 
> > > > > > > > Thanks
> > > > > > > > 
> > > > > > > > Here is a current config, I've been trying various versions.
> > > > > > > > 
> > > > > > > > name: stage01
> > > > > > > > 
> > > > > > > > cluster:  
> > > > > > > > name: esstagetest
> > > > > > > > 
> > > > > > > > node:  
> > > > > > > > data: true
> > > > > > > > 
> > > > > > > > http:  
> > > > > > > > enabled: true
> > > > > > > > 
> > > > > > > > gateway:  
> > > > > > > > type: fs  
> > > > > > > > fs:  
> > > > > > > > location: /home/esearch/gateway/indices
> > > > > > > > 
> > > > > > > > index :  
> > > > > > > > gateawy:  
> > > > > > > > snapshot\_interval: 30s  
> > > > > > > > number\_of\_shards : 5  
> > > > > > > > number\_of\_replicas : 4  
> > > > > > > > analysis :  
> > > > > > > > analyzer :  
> > > > > > > > standard :  
> > > > > > > > type : standard
> > > > > > > > 
> > > > > > > > store:  
> > > > > > > > type: memory  
> > > > > > > > memory:  
> > > > > > > > cache\_size: 100m  
> > > > > > > > buffer\_size: 10k
> > > > > > > > 
> > > > > > > > #discovery:
> > > > > > > > 
> > > > > > > > # zen:
> > > > > > > > 
> > > > > > > > # ping:
> > > > > > > > 
> > > > > > > > # multicast:
> > > > > > > > 
> > > > > > > > # enabled: false
> > > > > > > > 
> > > > > > > > # unicast:
> > > > > > > > 
> > > > > > > > # hosts: ["stage01:9301", "stage02:9302"]
> > > > > > > > 
> > > > > > > > transport:  
> > > > > > > > tcp:  
> > > > > > > > port: 9300
> > > > > > > > 
> > > > > > > > path:  
> > > > > > > > logs: /home/esearch/gateway/logs/stage01
> > > > > > > > 
> > > > > > > > On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon \<  
> > > > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > > > 
> > > > > > > > > Can you post your unicast configuration? In general, you can  
> > > > > > > > > set discovery.zen to TRACE to see whats going on...
> > > > > > > > > 
> > > > > > > > > On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle \<  
> > > > > > > > > [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)\> wrote:
> > > > > > > > > 
> > > > > > > > > > I am testing in a staging environment with several servers but  
> > > > > > > > > > have unable to successfully get Elasticsearch to recognize each peer.  
> > > > > > > > > > Multicast is enabled and being used by other parts of our  
> > > > > > > > > > application. I have also tried going the unicast route with Elasticsearch  
> > > > > > > > > > after disabling multicast with no luck.

---

<div class="post-metadata">

**Author:** ![Samuel\_Doyle](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@Samuel\_Doyle](https://discuss.elastic.co/u/Samuel_Doyle)\
**Post date:** [July 26, 2010, 12:16am UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/12 "2010-07-26T00:16:38Z")

</div>

Disregard this, the ip address wasn't set due to a config error I had, I  
still seem to not be able to set the port however.

Thanks

On Sun, Jul 25, 2010 at 4:59 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com) wrote:

> I've also tried setting the address for multicast seems I have no control  
> over what it does.
> 
> On Sun, Jul 25, 2010 at 4:46 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> 
> > If I specify a network: [some ip address] it then publishes on another  
> > differently nic:
> > 
> > [18:44:09,586][INFO][http] [stage01] bound\_address  
> > {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/192.168.122.1:9200  
> > ]}  
> > [18:44:09,795][INFO][jmx] [stage01] bound\_address  
> > {service:jmx:rmi:///jndi/rmi://:9400/jmxrmi}, publish\_address  
> > {service:jmx:rmi:///jndi/rmi://192.168.122.1:9400/jmxrmi}
> > 
> > That is not the ip or nic I specify
> > 
> > On Sun, Jul 25, 2010 at 4:38 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > 
> > > How do I control which port it publishes to, it doesn't appear I have any  
> > > control over that.
> > > 
> > > Thanks
> > > 
> > > On Sun, Jul 25, 2010 at 3:02 PM, Shay Banon \<  
> > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > 
> > > > Basically, when you start a node, you see the transport module prints  
> > > > the publish address it uses, this address should be used in the hosts list.
> > > > 
> > > > -shay.banon
> > > > 
> > > > On Mon, Jul 26, 2010 at 12:50 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > > 
> > > > > I had tried various configurations this is just the latest, I tried  
> > > > > 9300 as well wasn't sure about that.
> > > > > 
> > > > > On Sun, Jul 25, 2010 at 2:40 PM, Shay Banon \<  
> > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > 
> > > > > > Just saw that (I assume) the configuration you set for stage01 is to  
> > > > > > start on port 9300, yet you configure it in the unicast hosts with port  
> > > > > > 9301. Is that intentional?
> > > > > > 
> > > > > > -shay.banon
> > > > > > 
> > > > > > On Mon, Jul 26, 2010 at 12:38 AM, Samuel Doyle \<[samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)
> > > > > > 
> > > > > > > wrote:
> > > > > > 
> > > > > > > Yeah I tried that as well, no luck.
> > > > > > > 
> > > > > > > On Sun, Jul 25, 2010 at 12:32 PM, Shay Banon \<  
> > > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > > 
> > > > > > > > Can you try and replace stage01 and stage02 with the actual IPs,  
> > > > > > > > maybe they are not resolved properly?
> > > > > > > > 
> > > > > > > > On Sun, Jul 25, 2010 at 10:06 PM, Samuel Doyle \<  
> > > > > > > > [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)\> wrote:
> > > > > > > > 
> > > > > > > > > Ah great, I'll give that a shot to see if I can get some more info.
> > > > > > > > > 
> > > > > > > > > Thanks
> > > > > > > > > 
> > > > > > > > > Here is a current config, I've been trying various versions.
> > > > > > > > > 
> > > > > > > > > name: stage01
> > > > > > > > > 
> > > > > > > > > cluster:  
> > > > > > > > > name: esstagetest
> > > > > > > > > 
> > > > > > > > > node:  
> > > > > > > > > data: true
> > > > > > > > > 
> > > > > > > > > http:  
> > > > > > > > > enabled: true
> > > > > > > > > 
> > > > > > > > > gateway:  
> > > > > > > > > type: fs  
> > > > > > > > > fs:  
> > > > > > > > > location: /home/esearch/gateway/indices
> > > > > > > > > 
> > > > > > > > > index :  
> > > > > > > > > gateawy:  
> > > > > > > > > snapshot\_interval: 30s  
> > > > > > > > > number\_of\_shards : 5  
> > > > > > > > > number\_of\_replicas : 4  
> > > > > > > > > analysis :  
> > > > > > > > > analyzer :  
> > > > > > > > > standard :  
> > > > > > > > > type : standard
> > > > > > > > > 
> > > > > > > > > store:  
> > > > > > > > > type: memory  
> > > > > > > > > memory:  
> > > > > > > > > cache\_size: 100m  
> > > > > > > > > buffer\_size: 10k
> > > > > > > > > 
> > > > > > > > > #discovery:
> > > > > > > > > 
> > > > > > > > > # zen:
> > > > > > > > > 
> > > > > > > > > # ping:
> > > > > > > > > 
> > > > > > > > > # multicast:
> > > > > > > > > 
> > > > > > > > > # enabled: false
> > > > > > > > > 
> > > > > > > > > # unicast:
> > > > > > > > > 
> > > > > > > > > # hosts: ["stage01:9301", "stage02:9302"]
> > > > > > > > > 
> > > > > > > > > transport:  
> > > > > > > > > tcp:  
> > > > > > > > > port: 9300
> > > > > > > > > 
> > > > > > > > > path:  
> > > > > > > > > logs: /home/esearch/gateway/logs/stage01
> > > > > > > > > 
> > > > > > > > > On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon \<  
> > > > > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > > > > 
> > > > > > > > > > Can you post your unicast configuration? In general, you can  
> > > > > > > > > > set discovery.zen to TRACE to see whats going on...
> > > > > > > > > > 
> > > > > > > > > > On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle \<  
> > > > > > > > > > [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)\> wrote:
> > > > > > > > > > 
> > > > > > > > > > > I am testing in a staging environment with several servers but  
> > > > > > > > > > > have unable to successfully get Elasticsearch to recognize each peer.  
> > > > > > > > > > > Multicast is enabled and being used by other parts of our  
> > > > > > > > > > > application. I have also tried going the unicast route with Elasticsearch  
> > > > > > > > > > > after disabling multicast with no luck.

---

<div class="post-metadata">

**Author:** ![Samuel\_Doyle](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@Samuel\_Doyle](https://discuss.elastic.co/u/Samuel_Doyle)\
**Post date:** [July 26, 2010, 12:43am UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/13 "2010-07-26T00:43:37Z")

</div>

Ok it doesn't really matter the port, I was able to get the multicast  
working. There are several nics on the servers we have all which indicate  
that multicast is enabled (or so when I do an ifconfig) but there was some  
configuration required on one nic on each server which is specific to our  
private network. The support at our colo. applied whatever changes needed  
and it is fine now.

Thanks for your help again

On Sun, Jul 25, 2010 at 5:16 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com) wrote:

> Disregard this, the ip address wasn't set due to a config error I had, I  
> still seem to not be able to set the port however.
> 
> Thanks
> 
> On Sun, Jul 25, 2010 at 4:59 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> 
> > I've also tried setting the address for multicast seems I have no control  
> > over what it does.
> > 
> > On Sun, Jul 25, 2010 at 4:46 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > 
> > > If I specify a network: [some ip address] it then publishes on another  
> > > differently nic:
> > > 
> > > [18:44:09,586][INFO][http] [stage01] bound\_address  
> > > {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/192.168.122.1:9200  
> > > ]}  
> > > [18:44:09,795][INFO][jmx] [stage01] bound\_address  
> > > {service:jmx:rmi:///jndi/rmi://:9400/jmxrmi}, publish\_address  
> > > {service:jmx:rmi:///jndi/rmi://192.168.122.1:9400/jmxrmi}
> > > 
> > > That is not the ip or nic I specify
> > > 
> > > On Sun, Jul 25, 2010 at 4:38 PM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > 
> > > > How do I control which port it publishes to, it doesn't appear I have  
> > > > any control over that.
> > > > 
> > > > Thanks
> > > > 
> > > > On Sun, Jul 25, 2010 at 3:02 PM, Shay Banon \<  
> > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > 
> > > > > Basically, when you start a node, you see the transport module prints  
> > > > > the publish address it uses, this address should be used in the hosts list.
> > > > > 
> > > > > -shay.banon
> > > > > 
> > > > > On Mon, Jul 26, 2010 at 12:50 AM, Samuel Doyle [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)wrote:
> > > > > 
> > > > > > I had tried various configurations this is just the latest, I tried  
> > > > > > 9300 as well wasn't sure about that.
> > > > > > 
> > > > > > On Sun, Jul 25, 2010 at 2:40 PM, Shay Banon \<  
> > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > 
> > > > > > > Just saw that (I assume) the configuration you set for stage01 is to  
> > > > > > > start on port 9300, yet you configure it in the unicast hosts with port  
> > > > > > > 9301. Is that intentional?
> > > > > > > 
> > > > > > > -shay.banon
> > > > > > > 
> > > > > > > On Mon, Jul 26, 2010 at 12:38 AM, Samuel Doyle \<  
> > > > > > > [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)\> wrote:
> > > > > > > 
> > > > > > > > Yeah I tried that as well, no luck.
> > > > > > > > 
> > > > > > > > On Sun, Jul 25, 2010 at 12:32 PM, Shay Banon \<  
> > > > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > > > 
> > > > > > > > > Can you try and replace stage01 and stage02 with the actual IPs,  
> > > > > > > > > maybe they are not resolved properly?
> > > > > > > > > 
> > > > > > > > > On Sun, Jul 25, 2010 at 10:06 PM, Samuel Doyle \<  
> > > > > > > > > [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)\> wrote:
> > > > > > > > > 
> > > > > > > > > > Ah great, I'll give that a shot to see if I can get some more  
> > > > > > > > > > info.
> > > > > > > > > > 
> > > > > > > > > > Thanks
> > > > > > > > > > 
> > > > > > > > > > Here is a current config, I've been trying various versions.
> > > > > > > > > > 
> > > > > > > > > > name: stage01
> > > > > > > > > > 
> > > > > > > > > > cluster:  
> > > > > > > > > > name: esstagetest
> > > > > > > > > > 
> > > > > > > > > > node:  
> > > > > > > > > > data: true
> > > > > > > > > > 
> > > > > > > > > > http:  
> > > > > > > > > > enabled: true
> > > > > > > > > > 
> > > > > > > > > > gateway:  
> > > > > > > > > > type: fs  
> > > > > > > > > > fs:  
> > > > > > > > > > location: /home/esearch/gateway/indices
> > > > > > > > > > 
> > > > > > > > > > index :  
> > > > > > > > > > gateawy:  
> > > > > > > > > > snapshot\_interval: 30s  
> > > > > > > > > > number\_of\_shards : 5  
> > > > > > > > > > number\_of\_replicas : 4  
> > > > > > > > > > analysis :  
> > > > > > > > > > analyzer :  
> > > > > > > > > > standard :  
> > > > > > > > > > type : standard
> > > > > > > > > > 
> > > > > > > > > > store:  
> > > > > > > > > > type: memory  
> > > > > > > > > > memory:  
> > > > > > > > > > cache\_size: 100m  
> > > > > > > > > > buffer\_size: 10k
> > > > > > > > > > 
> > > > > > > > > > #discovery:
> > > > > > > > > > 
> > > > > > > > > > # zen:
> > > > > > > > > > 
> > > > > > > > > > # ping:
> > > > > > > > > > 
> > > > > > > > > > # multicast:
> > > > > > > > > > 
> > > > > > > > > > # enabled: false
> > > > > > > > > > 
> > > > > > > > > > # unicast:
> > > > > > > > > > 
> > > > > > > > > > # hosts: ["stage01:9301", "stage02:9302"]
> > > > > > > > > > 
> > > > > > > > > > transport:  
> > > > > > > > > > tcp:  
> > > > > > > > > > port: 9300
> > > > > > > > > > 
> > > > > > > > > > path:  
> > > > > > > > > > logs: /home/esearch/gateway/logs/stage01
> > > > > > > > > > 
> > > > > > > > > > On Sun, Jul 25, 2010 at 11:52 AM, Shay Banon \<  
> > > > > > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > > > > > 
> > > > > > > > > > > Can you post your unicast configuration? In general, you can  
> > > > > > > > > > > set discovery.zen to TRACE to see whats going on...
> > > > > > > > > > > 
> > > > > > > > > > > On Sun, Jul 25, 2010 at 8:08 PM, Samuel Doyle \<  
> > > > > > > > > > > [samueldoyle@gmail.com](mailto:samueldoyle@gmail.com)\> wrote:
> > > > > > > > > > > 
> > > > > > > > > > > > I am testing in a staging environment with several servers but  
> > > > > > > > > > > > have unable to successfully get Elasticsearch to recognize each peer.  
> > > > > > > > > > > > Multicast is enabled and being used by other parts of our  
> > > > > > > > > > > > application. I have also tried going the unicast route with Elasticsearch  
> > > > > > > > > > > > after disabling multicast with no luck.

---

<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:** [July 6, 2017, 4:21am UTC](https://discuss.elastic.co/t/anyone-have-issues-with-node-communication-in-a-cluster/3149/14 "2017-07-06T04:21:38Z")

</div>