# Running cluster replication over flaky connection

**URL:** <https://discuss.elastic.co/t/running-cluster-replication-over-flaky-connection/8814>\
**Category:** Elasticsearch\
**Created:** [August 22, 2012, 1:57pm UTC](https://discuss.elastic.co/t/running-cluster-replication-over-flaky-connection/8814 "2012-08-22T13:57:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mikhail\_Sayapin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_sayapin/32/2758_2.png) [@Mikhail\_Sayapin](https://discuss.elastic.co/u/Mikhail_Sayapin)\
**Post date:** [August 22, 2012, 1:57pm UTC](https://discuss.elastic.co/t/running-cluster-replication-over-flaky-connection/8814/1 "2012-08-22T13:57:17Z")

</div>

Hello everyone,

I have a PC at home in China, which is downloading some data from Chinese  
websites and processing it for further use. On the same PC there is an ES  
master node, which indexes these data.

Another server in Europe is holding the copy of the index, and used only  
for reading.

So basically Chinese server is Master, and Europe server is slave.

The connection is very flaky and slow, bandwidth (256 kbit, yes) is ok, but  
sometimes network splits, and the packet loss is about 5%.

Could you please advise what network and cluster settings I should tweak to  
ensure seamless operation?

I'm thinking of setting "transport.tcp.compress" to true, of course. Also I  
believe I should set data: true for the Europe node. Beyong that I'm a bit  
lost and would appreciate any input.

Thanks!

--

---

<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, 3:15am UTC](https://discuss.elastic.co/t/running-cluster-replication-over-flaky-connection/8814/2 "2017-07-06T03:15:30Z")

</div>