# Hardware requirements for production cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [March 1, 2019, 10:28am UTC](https://discuss.elastic.co/t/hardware-requirements-for-production-cluster/170478 "2019-03-01T10:28:27Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [March 1, 2019, 1:58pm UTC](https://discuss.elastic.co/t/hardware-requirements-for-production-cluster/170478/2 "2019-03-01T13:58:13Z")
> [@stevesimpson](#): > > My first question is this; Does the above look appropriate for a cluster ingesting around 20-30GB per day, with the view to expanding this to include system metrics, audit logs and heartbeat checks? Only benchmarking with a realistic workload can say for sure, but my initial impression is that this sounds like a lot of power for the load you describe. Each of your SSD-based "hot" nodes already has enough storage for a year's worth of data at that rate. Do you need the "warm" tier at all? Do you need three data nodes or would two be enough? > [@stevesimpson](#): > > Secondly I am considering adding 3x Coordinator nodes which will also run Kibana pointed to localhost. These will sit behind HAProxy loadbalancers to provide load balancing and high availability. You focussed on ingest load rather than search. Does this mean you expect the search load to be relatively light? If so, again, 3x coordinating nodes sounds excessive. Perhaps you can just search on the data nodes directly (via your load balancer)? Again, only benchmarking with a realistic workload can say for sure. > [@stevesimpson](#): > > Am I correct in this assumption that Kibana would only be able to point to a single data node to perform queries without the coordinator? It [sounds like](https://discuss.elastic.co/t/kibana-with-multinode-elasticsearch-cluster/75337/2) you can put a load balancer between your Kibana nodes and the Elasticsearch nodes, although the recommended architecture is to point each Kibana at a single node. > [@stevesimpson](#): > > My final question is this; what kind of resources should I be looking at for the coordinator nodes in relating to the rest of the stack? My thinking was something slightly more powerful that the Master nodes but not as "beefy" as the data nodes. They won't need much disk but will use a decent amount of RAM if you are going to hit them hard with lots of heavy aggregations or other expensive searches. --- _[View the full topic](https://discuss.elastic.co/t/hardware-requirements-for-production-cluster/170478)._