# Scalability of ES server

**URL:** <https://discuss.elastic.co/t/scalability-of-es-server/237329>\
**Category:** Elasticsearch\
**Created:** [June 16, 2020, 3:20pm UTC](https://discuss.elastic.co/t/scalability-of-es-server/237329 "2020-06-16T15:20:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andre\_Dexheimer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andre_dexheimer/32/70469_2.png) [@Andre\_Dexheimer](https://discuss.elastic.co/u/Andre_Dexheimer)\
**Post date:** [June 16, 2020, 3:20pm UTC](https://discuss.elastic.co/t/scalability-of-es-server/237329/1 "2020-06-16T15:20:16Z")

</div>

Hi,

I'm running a setup with Elasticsearch, Fluentd and Kibana where a single central aggregator receives data from multiple clients and stores it into elasticsearch, running in a docker compose.

I receive about 22GB of data per day. Currently, I'm having some issues with clients disconnecting and I'm not sure exactly what the cause is.

So I'm wondering if it could be a hardware limitation and also how much more data I could store and index with this setup as demand grows.

Basically, the settings are:  
1 index, 1 shard, 1 replica  
16GB RAM, with JVM heap size set to 10GB  
4 core/4 thread Intel Xeon Platinum 8171M CPU @ 2.60GHz  
HDD

Thanks in advance

---

<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 14, 2020, 3:20pm UTC](https://discuss.elastic.co/t/scalability-of-es-server/237329/2 "2020-07-14T15:20:18Z")

</div>

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