# Indexing very large and searchable documents

**URL:** <https://discuss.elastic.co/t/indexing-very-large-and-searchable-documents/202527>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [October 7, 2019, 12:18pm UTC](https://discuss.elastic.co/t/indexing-very-large-and-searchable-documents/202527 "2019-10-07T12:18:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mmaury](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mmaury/32/36671_2.png) [@mmaury](https://discuss.elastic.co/u/mmaury)\
**Post date:** [October 7, 2019, 12:18pm UTC](https://discuss.elastic.co/t/indexing-very-large-and-searchable-documents/202527/1 "2019-10-07T12:18:11Z")

</div>

Hi there !

Has someone already tried to index very large documents in Elasticsearch (\>300Mo) ?  
When we try, we've got an OutOfMemoryException, with GC messages.

`[INFO][o.e.m.j.JvmGcMonitorService] [KR7Jg8N] [gc][1395] overhead, spent [331ms] collecting in the last [1s]`  
`[WARN][o.e.m.j.JvmGcMonitorService] [KR7Jg8N] [gc][old][1415][22] duration [41.8s], collections [1]/[42.1s], total [41.8s]/[8.5m], memory [15.9gb]->[15.9gb]/[15.9gb], all_pools {[young] [124mb]->[127.6mb]/[133.1mb]}{[survivor] [0b]->[0b]/[16.6mb]}{[old] [15.8gb]->[15.8gb]/[15.8gb]}`

In dev mode we're using 1 node (ES 6.5) with Xmx 16Go RAM, with Docker.

We saw the `http.max_content_length` param and have already increase it to 600mb.  
[https://www.elastic.co/guide/en/elasticsearch/reference/6.5/modules-http.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.5/modules-http.html)

Has someone a feedback and technical recommendations for dealing with it ?

Thanks.

---

<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:** [November 4, 2019, 12:18pm UTC](https://discuss.elastic.co/t/indexing-very-large-and-searchable-documents/202527/2 "2019-11-04T12:18:17Z")

</div>

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