# Avoid partial success of bulk Ingests under load

**URL:** <https://discuss.elastic.co/t/avoid-partial-success-of-bulk-ingests-under-load/184179>\
**Category:** Elasticsearch\
**Created:** [June 4, 2019, 12:42pm UTC](https://discuss.elastic.co/t/avoid-partial-success-of-bulk-ingests-under-load/184179 "2019-06-04T12:42:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sreekanth](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@sreekanth](https://discuss.elastic.co/u/sreekanth)\
**Post date:** [June 4, 2019, 12:42pm UTC](https://discuss.elastic.co/t/avoid-partial-success-of-bulk-ingests-under-load/184179/1 "2019-06-04T12:42:46Z")

</div>

Under heavy loads we observed that few bulk ingests are returning status code of 200. But If we look at their response content, we see "errors=true". And out of 100 requests, few failed with 429 errors. So this is a partial success.

Is there any way to make sure that all requests pass or fail rather few pass few fail. So that I can retry the bulk again rather parsing the response and trying to resubmit for those failed alone?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [June 4, 2019, 2:24pm UTC](https://discuss.elastic.co/t/avoid-partial-success-of-bulk-ingests-under-load/184179/2 "2019-06-04T14:24:43Z")

</div>

No, different part are executed on different nodes so it is always possible to have partial failures. There is no atomicity for bulk requests.

---

<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:** [July 2, 2019, 2:24pm UTC](https://discuss.elastic.co/t/avoid-partial-success-of-bulk-ingests-under-load/184179/3 "2019-07-02T14:24:44Z")

</div>

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