# ConnectTransportException: Data member unable to connect to secondary almost nightly

**URL:** <https://discuss.elastic.co/t/connecttransportexception-data-member-unable-to-connect-to-secondary-almost-nightly/11599>\
**Category:** Elasticsearch\
**Created:** [April 16, 2013, 1:29pm UTC](https://discuss.elastic.co/t/connecttransportexception-data-member-unable-to-connect-to-secondary-almost-nightly/11599 "2013-04-16T13:29:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Darius\_Riggins](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darius_riggins/32/2374_2.png) [@Darius\_Riggins](https://discuss.elastic.co/u/Darius_Riggins)\
**Post date:** [April 16, 2013, 1:29pm UTC](https://discuss.elastic.co/t/connecttransportexception-data-member-unable-to-connect-to-secondary-almost-nightly/11599/1 "2013-04-16T13:29:02Z")

</div>

I have a 4 node cluster, and almost nightly I have at least one of my  
primary members that just suddenly stops being able to communicate with the  
other nodes. The logs don't seem to tell me why, but maybe I'm missing  
something. I've created a gist with the config of the primary and  
secondaries, along with the error log. I checked my system logs, and there  
was no reboot or significant event that occurred last night. Stopping the  
data: false, master: true node that couldn't communicate and starting it  
again resolves the issue.

[https://gist.github.com/dariusriggins/5395798](https://gist.github.com/dariusriggins/5395798)

ElasticSearch Version: 0.20.5  
JVM Version: 7.0.170.2  
OS: Windows Server 2008 R2

Cluster Status:  
{  
ok: true  
cluster\_name: engagetv  
nodes: {  
cHPuvetUT0CPcgc5xYLX0g: {  
name: Myers, Fred  
transport\_address: inet[/10.191.252.183:9300]  
hostname: SSCASQAENGTV01  
version: 0.20.5  
http\_address: inet[/10.191.252.183:9200]  
attributes: {  
data: false  
master: true  
}  
}  
3TXf-DCVSzKS0dO621JV5g: {  
name: Harald Jaekelsson  
transport\_address: inet[/10.191.252.184:9300]  
hostname: SSCASQAENGTV02  
version: 0.20.5  
http\_address: inet[/10.191.252.184:9200]  
attributes: {  
master: false  
}  
}  
8G2xRxs5TJyDCk8r9wzEvg: {  
name: Razor Fist  
transport\_address: inet[/10.191.252.185:9300]  
hostname: SSCASQAENGTV03  
version: 0.20.5  
http\_address: inet[/10.191.252.185:9200]  
attributes: {  
data: false  
master: true  
}  
}  
O\_H2rOR9Q9u8HVH7GJuYmw: {  
name: van Lunt, Cornelius  
transport\_address: inet[/10.191.252.186:9300]  
hostname: SSCASQAENGTV04  
version: 0.20.5  
http\_address: inet[/10.191.252.186:9200]  
attributes: {  
master: false  
}  
}  
}  
}

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 2:40am UTC](https://discuss.elastic.co/t/connecttransportexception-data-member-unable-to-connect-to-secondary-almost-nightly/11599/2 "2017-07-06T02:40:57Z")

</div>

Closed on July 6, 2017, 2:40am UTC