# Is ElasticSearch meant for long term storage of large datasets?

**URL:** https://discuss.elastic.co/t/is-elasticsearch-meant-for-long-term-storage-of-large-datasets/220477
**Category:** Elasticsearch
**Created:** [February 22, 2020, 9:36am UTC](https://discuss.elastic.co/t/is-elasticsearch-meant-for-long-term-storage-of-large-datasets/220477 "2020-02-22T09:36:36Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Basman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/basman/32/63140_2.png) [@Basman](https://discuss.elastic.co/u/Basman)
#### Post date: [February 22, 2020, 9:36am UTC](https://discuss.elastic.co/t/is-elasticsearch-meant-for-long-term-storage-of-large-datasets/220477/1 "2020-02-22T09:36:36Z")

</div>

I have users that all have hundreds of GB’s of documents (pdf, word, etc). I want to use Elastic with the ingest-attachment plugin to make the plaintext contents of these documents searchable. It’s unlikely these documents will eventually be deleted, so the dataset will mostly get bigger.

My question: is this a usecase that Elastic can safely handle? Or will I eventually run into a wall of sorts if the data set gets too big? The thing I’m mostly worried about is that searching for text will get slower if users upload too many documents.

---

<div class="post-metadata">

### 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: [February 22, 2020, 12:16pm UTC](https://discuss.elastic.co/t/is-elasticsearch-meant-for-long-term-storage-of-large-datasets/220477/2 "2020-02-22T12:16:34Z")

</div>

Hundreds of GBs is not really a "large" dataset in Elasticsearch terms; you can search [TBs of data with a single node](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster) and there are clusters out there containing PBs of data that ingest hundreds of GBs of new documents every hour.

Moreover PDFs and Word documents typically contain a lot of unsearchable overhead, so the size of the plaintext content that Elasticsearch actually sees is often many times smaller than the total file size.

I'm not saying that there are no scaling limits, of course, and this all depends on your usage pattern and performance goals too, but in terms of data size alone you're well within the comfort zone.

---

<div class="post-metadata">

### Author: ![Basman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/basman/32/63140_2.png) [@Basman](https://discuss.elastic.co/u/Basman)
#### Post date: [February 22, 2020, 1:34pm UTC](https://discuss.elastic.co/t/is-elasticsearch-meant-for-long-term-storage-of-large-datasets/220477/3 "2020-02-22T13:34:16Z")

</div>

Excellent, thanks for the feedback.

---

<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: [March 21, 2020, 1:34pm UTC](https://discuss.elastic.co/t/is-elasticsearch-meant-for-long-term-storage-of-large-datasets/220477/4 "2020-03-21T13:34:16Z")

</div>

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