# Optimal Cluster for Production **URL:** \ **Category:** Elasticsearch\ **Created:** [August 8, 2024, 5:17pm UTC](https://discuss.elastic.co/t/optimal-cluster-for-production/364618 "2024-08-08T17:17:16Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![fatima1](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fatima1](https://discuss.elastic.co/u/fatima1)\ **Post date:** [August 8, 2024, 5:17pm UTC](https://discuss.elastic.co/t/optimal-cluster-for-production/364618/1 "2024-08-08T17:17:16Z")
I am overseeing a production cluster consisting of approximately 83 nodes, and we are handling nearly a million of data points daily . To optimize the production environment, what are the recommended best practices regarding hardware specifications? Specifically, how many data nodes should be employed, how much RAM should each machine have, and what other hardware specifications should be considered for optimal performance? ---
**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:** [August 13, 2024, 7:47am UTC](https://discuss.elastic.co/t/optimal-cluster-for-production/364618/2 "2024-08-13T07:47:40Z")
This will depend a lot on the use case, data volumes, type of data and the type of load and latencies the cluster must serve. As you have a current production cluster it is probably good to start by looking at how this is performing and identifying any potential performance issues or where there may be excessive capacity. You will need to provide a lot more information about the use case, including data, query and indexing volumes for someone to be able to give any recommendations. Information about the setup and configuration of the current cluster and how it is performing would also be useful. A good way to provide an overview of the cluster is to provide the full output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-stats.html). > [@fatima1](#): > > we are handling nearly a million of data points daily It is not clear what you mean by this. Indexing one million documents per day in a 83 node cluster sounds like very light indexing load. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [August 13, 2024, 7:59am UTC](https://discuss.elastic.co/t/optimal-cluster-for-production/364618/3 "2024-08-13T07:59:44Z")
> [@Christian\_Dahlqvist](#): > > Indexing one million documents per day in a 83 node cluster sounds like very light indexing load. ++ for instance [this benchmark](https://elasticsearch-benchmarks.elastic.co/index.html#tracks/http-logs/nightly/default/90d) involves a 3-node cluster with some configurations indexing about 200,000 documents per second. 1M/day seems very low even for a single node, let alone 83 nodes! ---
**Author:** ![fatima1](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fatima1](https://discuss.elastic.co/u/fatima1)\ **Post date:** [August 15, 2024, 2:38pm UTC](https://discuss.elastic.co/t/optimal-cluster-for-production/364618/4 "2024-08-15T14:38:30Z")
@Christian_Dahlqvist I’m currently facing data loss at the ingest node, where some data packets are being lost. Additionally, my data nodes are not being utilized evenly. I ingest a total of 1 TB of data each week, starting with a small amount that gradually increases to 1 TB, and this data is deleted after one week. @DavidTurner ---
**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:** [August 15, 2024, 2:42pm UTC](https://discuss.elastic.co/t/optimal-cluster-for-production/364618/5 "2024-08-15T14:42:25Z")
If you want someone to be able to help you will need to provide a lot more details than that about the current cluster, data volumes and indexing and query load. The full output of the API I linked to would be a good start. ---
**Author:** ![fatima1](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fatima1](https://discuss.elastic.co/u/fatima1)\ **Post date:** [August 15, 2024, 2:46pm UTC](https://discuss.elastic.co/t/optimal-cluster-for-production/364618/6 "2024-08-15T14:46:47Z")
i just want suggest or solution that why i am lossing data on ingest node .. is it related to hardware defficency ? do i need to increase SSD of system or do i need to use coordinating node before ingest node soo that may balance evenly and i dont face data loss ---
**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:** [August 15, 2024, 2:53pm UTC](https://discuss.elastic.co/t/optimal-cluster-for-production/364618/7 "2024-08-15T14:53:17Z")
Given that you are not willing to provide any information I would recommend you go through [the guide about tuning for indexing speed](https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-indexing-speed.html).[This webinar](https://www.elastic.co/webinars/elasticsearch-sizing-and-capacity-planning) might also be useful.