# Exception with TCP ports for Tribe Nodes

**URL:** <https://discuss.elastic.co/t/exception-with-tcp-ports-for-tribe-nodes/20369>\
**Category:** Elasticsearch\
**Created:** [October 21, 2014, 11:21pm UTC](https://discuss.elastic.co/t/exception-with-tcp-ports-for-tribe-nodes/20369 "2014-10-21T23:21:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sagarit2](https://avatars.discourse-cdn.com/v4/letter/s/f0a364/32.png) [@sagarit2](https://discuss.elastic.co/u/sagarit2)\
**Post date:** [October 21, 2014, 11:21pm UTC](https://discuss.elastic.co/t/exception-with-tcp-ports-for-tribe-nodes/20369/1 "2014-10-21T23:21:10Z")

</div>

Hi,

I am using following yaml settings for Tribe Node:

node.name: es\_tribenode  
http.port: 7774  
tribe.t0.cluster.name: source\_cluster1  
tribe.t0.transport.tcp.port: 7709  
tribe.t1.cluster.name: source\_cluster2  
tribe.t1.transport.tcp.port: 7709

Both the source clusters are running with _tcp.port = 7709_, hence I added  
the setting _tribe.t0.transport.tcp.port_\*: 7709\* and  
_tribe.t1.transport.tcp.port_\*: 7709\*, respectively for each cluster. So  
that Tribe Node can connect to source cluster nodes over _7709_.

But the problem arises when ES creates individual internal nodes for both  
clusters.

First internal node (es\_tribenode/t0) is bound to 7709 port.

And when ES tries to create Second internal node (es\_tribenode/t1) , it  
fails with bind exception. Because it tries to bind 7709 port to Second  
internal node. And this port is already taken by First internal node.  
_org.elasticsearch.transport.BindTransportException: Failed to  
bind to [7709]_

My question is that, is there any way to control ports of internal nodes  
via yml settings ? (without changing source cluster ports so that source  
clusters keep running on the same port)

Thanks,

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/28c2deed-92f0-421f-a0de-16f0649ecbf5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/28c2deed-92f0-421f-a0de-16f0649ecbf5%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 12:54am UTC](https://discuss.elastic.co/t/exception-with-tcp-ports-for-tribe-nodes/20369/2 "2017-07-06T00:54:35Z")

</div>