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

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]

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