# Elasticsearch inbound/outbound traffic

**URL:** <https://discuss.elastic.co/t/elasticsearch-inbound-outbound-traffic/308352>\
**Category:** Elasticsearch\
**Created:** [June 28, 2022, 11:47am UTC](https://discuss.elastic.co/t/elasticsearch-inbound-outbound-traffic/308352 "2022-06-28T11:47:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anton\_Schleenvoigt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anton_schleenvoigt/32/98900_2.png) [@Anton\_Schleenvoigt](https://discuss.elastic.co/u/Anton_Schleenvoigt)\
**Post date:** [June 28, 2022, 11:47am UTC](https://discuss.elastic.co/t/elasticsearch-inbound-outbound-traffic/308352/1 "2022-06-28T11:47:50Z")

</div>

Hi,

I'm trying to find out the amount of data produced for internal traffic between elasticsearch nodes. Did not find any useful on internet, and i always think that someone have been playing around with this type of questions before.

My setup: helm install from bitnami.  
kubernetes 1.23

elastisearch-master-0  
elastisearch-master-1  
elastisearch-master-2  
elasticsearch-data-0  
elasticsearch-data-1  
elasticsearch-data-2  
elasticsearch-coordinating-only-0  
elasticsearch-coordinating-only-1  
elasticsearch-coordinating-only-2

My analys that i did was to monitor the networkinterface for each vxlan-calio with wireshark.  
and the end result was a bit higher then i expected.

during a 24H cycle in an idle system the data produced around 7gb. (no data written to shard etc)

The problem that i'm facing is that i will create a remote cluster with 4g/5g communications between nodes. And the overhead that i'm facing is bit to high to make is worth it.

---

<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:** [June 28, 2022, 12:36pm UTC](https://discuss.elastic.co/t/elasticsearch-inbound-outbound-traffic/308352/2 "2022-06-28T12:36:43Z")

</div>

> [@Anton\_Schleenvoigt](#):
>
> The problem that i'm facing is that i will create a remote cluster with 4g/5g communications between nodes.

Elasticsearch requires low latency network with good bandwidth between the nodes of a cluster as well as the nodes reliably being available for resiliency and performance. Deploying over 4G/5G sounds like a very bad idea.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 28, 2022, 11:50pm UTC](https://discuss.elastic.co/t/elasticsearch-inbound-outbound-traffic/308352/3 "2022-06-28T23:50:28Z")

</div>

A _ **very** _ bad idea.

---

<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 26, 2022, 11:50pm UTC](https://discuss.elastic.co/t/elasticsearch-inbound-outbound-traffic/308352/4 "2022-07-26T23:50:51Z")

</div>

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