# Can elastic support these requirments **URL:** https://discuss.elastic.co/t/can-elastic-support-these-requirments/108682 **Category:** Elasticsearch **Created:** [November 22, 2017, 9:21am UTC](https://discuss.elastic.co/t/can-elastic-support-these-requirments/108682 "2017-11-22T09:21:01Z") **Posts on this page:** 1 **Showing post:** 5
### Author: ![aholbreich](https://avatars.discourse-cdn.com/v4/letter/a/d6d6ee/32.png) [@aholbreich](https://discuss.elastic.co/u/aholbreich) #### Post date: [November 23, 2017, 10:13pm UTC](https://discuss.elastic.co/t/can-elastic-support-these-requirments/108682/5 "2017-11-23T22:13:26Z")
Ok. First things to check, wether your machines can be equiped with SSD drives... several per maschine. with ssd drives you can achive more than 10000/s per Hardware node... and maybe more... but it depend on many things... Here look at discussion with spinning disks.: > [@Increasing elasticsearch indexing rate](https://discuss.elastic.co/t/increasing-elasticsearch-indexing-rate/74071): > > I have created a 3 node cluster, 1 Master Node, 1 Coordinating Node and 1 Data Node. I am using Logstash 2.4, Elasticsearch 5.2 and Kibana 5.2. Logstash is reading data from Kafka and sending it to the ingest node. I am not doing any data processing in logstash or in the Coordinating Node. All are Citrix VM having same configuration of : Red Hat Linux-7 Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz 6 Cores 32 GB RAM 2 TB spinning media Logstash Config file : input { kafka { zk\_connect… Let's assume you will make 20000/s per Hardware node (2 Elasticsearch instances in Docker) then you need at least 10 Hardware nodes to deal with your peaks... But 200.000 /s is huge number, so much other apps and custom tools can have problem before Elasticsearch... But again 2 billions a day is huge number, in best case you start with 1/10 of this on smaller set and test how it behaves and scalles... Check this: > **[How we reindexed 36 billion documents in 5 days within the same Elasticsearch...](https://thoughts.t37.net/how-we-reindexed-36-billions-documents-in-5-days-within-the-same-elasticsearch-cluster-cd9c054d1db8)** > > This article and much more is now part of my FREE EBOOK Running Elasticsearch for Fun and Profit available on Github. Fork it, star it… More questions - what happens if you're cluster can't index 200.000 for 2 minutes, and starts rejecting bulk index request? How does your application react? Is it custom app? Logstash for example can deal with that... --- _[View the full topic](https://discuss.elastic.co/t/can-elastic-support-these-requirments/108682)._