# Indexing Large, Complex and Nested JSON Documents - Overhead Spent error

**URL:** <https://discuss.elastic.co/t/indexing-large-complex-and-nested-json-documents-overhead-spent-error/72534>\
**Category:** Elasticsearch\
**Created:** [January 23, 2017, 8:34pm UTC](https://discuss.elastic.co/t/indexing-large-complex-and-nested-json-documents-overhead-spent-error/72534 "2017-01-23T20:34:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![httpex](https://avatars.discourse-cdn.com/v4/letter/h/47e85d/32.png) [@httpex](https://discuss.elastic.co/u/httpex)\
**Post date:** [January 23, 2017, 8:34pm UTC](https://discuss.elastic.co/t/indexing-large-complex-and-nested-json-documents-overhead-spent-error/72534/1 "2017-01-23T20:34:55Z")

</div>

What's the trick to getting complex JSON documents bulk indexed? I just tried indexing 48k lines which is only a portion of what I really need indexed with a PUT, but get a "overhead spent" error. The JSON is valid.

[2017-01-23T12:23:56,015][INFO][o.e.m.j.JvmGcMonitorService] [yc1iPJR] [gc][114  
7] overhead, spent [371ms] collecting in the last [1s]

---

<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:** [February 20, 2017, 8:36pm UTC](https://discuss.elastic.co/t/indexing-large-complex-and-nested-json-documents-overhead-spent-error/72534/2 "2017-02-20T20:36:03Z")

</div>

Closed on February 20, 2017, 8:36pm UTC

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