# Doubts about hardware requirements for elasticsearch

**URL:** <https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545>\
**Category:** Elasticsearch\
**Created:** [June 3, 2020, 12:14pm UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545 "2020-06-03T12:14:43Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![eayala](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@eayala](https://discuss.elastic.co/u/eayala)\
**Post date:** [June 3, 2020, 12:14pm UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/1 "2020-06-03T12:14:43Z")

</div>

I'm trying to setup elasticsearch cluster. I will get maximum of 4GB of data every day.

So what will be hardware required to set up ElasticSearch 7.6.2 and kibana 7.6.2

What is ideal configuration for server- side RAM/Hard/disks/CPU.

I currently have a single node cluster with:

- Intel (R) Xeon (R) CPU E7- 4807 @ 1.87GHz CPU (s): 4
- 20GB RAM
- 1TB HDD.

As additional data, the logs will be collected by Decanter 2.0.0.

Appreciate your help!!

---

<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 4, 2020, 11:51pm UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/2 "2020-06-04T23:51:06Z")

</div>

Welcome to our community! 😃

If you are only using a single node cluster, that should be fine. But please use 7.7, it's the latest release 🙂

---

<div class="post-metadata">

**Author:** ![eayala](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@eayala](https://discuss.elastic.co/u/eayala)\
**Post date:** [June 4, 2020, 11:58pm UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/3 "2020-06-04T23:58:32Z")

</div>

Thank you very much for the welcome

With the previous configuration it would be enough to index 4 GB daily without having any type of problem.

How many documents per second should be indexed.

Thank you so much.

---

<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 5, 2020, 12:01am UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/4 "2020-06-05T00:01:29Z")

</div>

> [@eayala](#):
>
> How many documents per second should be indexed.

What do you mean?

---

<div class="post-metadata">

**Author:** ![eayala](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@eayala](https://discuss.elastic.co/u/eayala)\
**Post date:** [June 5, 2020, 12:04am UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/5 "2020-06-05T00:04:29Z")

</div>

How can I know how many documents per second my cluster is capable of indexing.

---

<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 5, 2020, 12:05am UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/6 "2020-06-05T00:05:42Z")

</div>

Ah ok, you will need to test that yourself as it's dependant on the hardware, use case etc 🙂

---

<div class="post-metadata">

**Author:** ![eayala](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@eayala](https://discuss.elastic.co/u/eayala)\
**Post date:** [June 5, 2020, 12:10am UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/7 "2020-06-05T00:10:41Z")

</div>

For example I tried indexing 31000 documents in a java test that pulls in parallel with decanter logs to elasticsearch and I see that when finishing the elasticsearch test it continues indexing like 20 minutes later and it doesn't index me almost in real time as I expected, and I don't know what it is the problem, is it due to disk speed or do I have to have more hadware.

---

<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 5, 2020, 12:46am UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/8 "2020-06-05T00:46:05Z")

</div>

> [@eayala](#):
>
> it continues indexing like 20 minutes later and it doesn't index me almost in real time

That's not how it works. As soon as your client has received a 200 response from Elasticsearch, then it's been indexed. What's happening after that might be merging, but it's hard to know without more information on what you are seeing.

---

<div class="post-metadata">

**Author:** ![eayala](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@eayala](https://discuss.elastic.co/u/eayala)\
**Post date:** [June 5, 2020, 2:11am UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/9 "2020-06-05T02:11:15Z")

</div>

My single node cluster has a shard with no replica, refresh\_interval: 30s was defined and  
each document is approximately 1 kb in size.

---

<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 5, 2020, 5:20am UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/10 "2020-06-05T05:20:55Z")

</div>

The first thing to check is that you have followed [these instructions](https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-indexing-speed.html), especially about using bulk requests (especially since you are using HDD storage). Elasticsearch is often limited by disk utilization as indexing and associated merging can be very I/O intensive.

---

<div class="post-metadata">

**Author:** ![eayala](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@eayala](https://discuss.elastic.co/u/eayala)\
**Post date:** [June 5, 2020, 1:18pm UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/11 "2020-06-05T13:18:40Z")

</div>

Thank you very much Christian\_Dahlqvist.  
I'm going to review those instructions.

---

<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 3, 2020, 1:18pm UTC](https://discuss.elastic.co/t/doubts-about-hardware-requirements-for-elasticsearch/235545/12 "2020-07-03T13:18:44Z")

</div>

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