# Handling 409 Exception -version conflict

**URL:** <https://discuss.elastic.co/t/handling-409-exception-version-conflict/141919>\
**Category:** Logstash\
**Created:** [July 27, 2018, 9:50am UTC](https://discuss.elastic.co/t/handling-409-exception-version-conflict/141919 "2018-07-27T09:50:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TANISHQ\_BATRA](https://avatars.discourse-cdn.com/v4/letter/t/eada6e/32.png) [@TANISHQ\_BATRA](https://discuss.elastic.co/u/TANISHQ_BATRA)\
**Post date:** [July 27, 2018, 9:50am UTC](https://discuss.elastic.co/t/handling-409-exception-version-conflict/141919/1 "2018-07-27T09:50:55Z")

</div>

Hi,  
In our use case , We have a document , which has a collection of nested documents named "notes".  
Each document can have nested notes upto 1000 under field"notes".  
So when multiple nested objects i.e notes are added while one time load. I am receiving lots of 409 errors i,e version conflict.  
I have added the retry\_on\_conflict:100 property as well but still 409 errors are comng up.

Is there any other way to catch these request and retry them later or so? or any other suggestions as I don't think retry\_on\_conflict value must be higher than 3-4. for Higher values I see Error:Attempted to send a bulk request to elasticsearch' but Elasticsearch appears to be unreachable or down! {:error\_message=\>"Elasticsearch Unreachable: [[http://xxxxxxx:9200/](http://xxxxxxx:9200/)][xxxx::SocketTimeout] Read timed out", :

---

<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:** [August 24, 2018, 9:50am UTC](https://discuss.elastic.co/t/handling-409-exception-version-conflict/141919/2 "2018-08-24T09:50:56Z")

</div>

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