# BulkProcessor insertions not happening in our environment

**URL:** <https://discuss.elastic.co/t/bulkprocessor-insertions-not-happening-in-our-environment/380028>\
**Category:** Elasticsearch\
**Created:** [July 11, 2025, 11:06am UTC](https://discuss.elastic.co/t/bulkprocessor-insertions-not-happening-in-our-environment/380028 "2025-07-11T11:06:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajathgubbi](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@rajathgubbi](https://discuss.elastic.co/u/rajathgubbi)\
**Post date:** [July 11, 2025, 11:06am UTC](https://discuss.elastic.co/t/bulkprocessor-insertions-not-happening-in-our-environment/380028/1 "2025-07-11T11:06:20Z")

</div>

We are creating the BulkProcessor object as shown below. While some upserts are processed successfully, subsequent upserts are not being completed. This issue is occurring in a high-scale environment where the upserts requests are high in number. We are adding requests using `bulkProcessor.add(request);`. When a heap dump was taken, we can see the requests present in the dump.

Are there any known issues with this approach, or have similar problems been reported previously?

For reference, we are using Elasticsearch version 6.8.12.

```auto
bulkProcessor = BulkProcessor.builder(bulkConsumer, getBulkProcessListener())
    .setBulkActions(2000)
    .setBulkSize(
        new ByteSizeValue(100, ByteSizeUnit.MB))
    .setFlushInterval(5) // in seconds
    .setConcurrentRequests(2).build();

```

---

<div class="post-metadata">

**Author:** ![Keith\_Massey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keith_massey/32/83666_2.png) [@Keith\_Massey](https://discuss.elastic.co/u/Keith_Massey)\
**Post date:** [July 11, 2025, 1:29pm UTC](https://discuss.elastic.co/t/bulkprocessor-insertions-not-happening-in-our-environment/380028/2 "2025-07-11T13:29:13Z")

</div>

BulkProcessor had some race conditions that could lead to deadlock. This caused us to stop using BulkProcessor inside Elasticsearch. I don't know that that's what you're hitting (the output of `kill -3` might show it), but I would stay away from BulkProcessor, and upgrade to a supported version as soon as possible.

---

<div class="post-metadata">

**Author:** ![rajathgubbi](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@rajathgubbi](https://discuss.elastic.co/u/rajathgubbi)\
**Post date:** [July 14, 2025, 3:52am UTC](https://discuss.elastic.co/t/bulkprocessor-insertions-not-happening-in-our-environment/380028/3 "2025-07-14T03:52:12Z")

</div>

Can you please let me know what is the supported version where the issues mentioned in BulkProcessor is fixed?

---

<div class="post-metadata">

**Author:** ![Keith\_Massey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keith_massey/32/83666_2.png) [@Keith\_Massey](https://discuss.elastic.co/u/Keith_Massey)\
**Post date:** [July 14, 2025, 2:01pm UTC](https://discuss.elastic.co/t/bulkprocessor-insertions-not-happening-in-our-environment/380028/4 "2025-07-14T14:01:46Z")

</div>

I think BulkProcessor was removed in 7.0. It's definitely gone by 8.0. The whole [Java client](https://www.elastic.co/docs/reference/elasticsearch/clients/java) has been replaced since 6.8.