# Avoid network overhead/bottleneck due to bulk returning all items

**URL:** <https://discuss.elastic.co/t/avoid-network-overhead-bottleneck-due-to-bulk-returning-all-items/151622>\
**Category:** Elasticsearch\
**Created:** [October 9, 2018, 11:57am UTC](https://discuss.elastic.co/t/avoid-network-overhead-bottleneck-due-to-bulk-returning-all-items/151622 "2018-10-09T11:57:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndreCimander](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrecimander/32/30386_2.png) [@AndreCimander](https://discuss.elastic.co/u/AndreCimander)\
**Post date:** [October 9, 2018, 11:57am UTC](https://discuss.elastic.co/t/avoid-network-overhead-bottleneck-due-to-bulk-returning-all-items/151622/1 "2018-10-09T11:57:34Z")

</div>

Is there a hidden request parameter for the bulk api to omit successful items in the `/bulk` response or get a sane response format (e.g. `success count, error count, optional list of errord documents`)?

When we send a 50MB bulk request to elasticsearch, we also receive a 50MB+ back in the response's item key, which is _kind of crazy_ for an endpoint that is designed for high throughput.

We are resorting to `?filter_path=errors`, but this breaks error identification and requires some ugly workarounds, and the coordinating node is still gathering all the items from the cluster.

---

<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 6, 2018, 11:57am UTC](https://discuss.elastic.co/t/avoid-network-overhead-bottleneck-due-to-bulk-returning-all-items/151622/2 "2018-11-06T11:57:36Z")

</div>

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