# ES VersionConflictEngineException current version \[-1\]
**URL:** https://discuss.elastic.co/t/es-versionconflictengineexception-current-version-1/311282
**Category:** Elasticsearch
**Created:** [August 3, 2022, 9:37am UTC](https://discuss.elastic.co/t/es-versionconflictengineexception-current-version-1/311282 "2022-08-03T09:37:08Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@zhcwang](https://discuss.elastic.co/u/zhcwang)
#### Post date: [August 3, 2022, 9:37am UTC](https://discuss.elastic.co/t/es-versionconflictengineexception-current-version-1/311282/1 "2022-08-03T09:37:08Z")
I am using ElasticSearch Cluster backed by 3 nodes and batch update several items in one run.
It reports version conflicts of one item, and the raw log is
```auto
VersionConflictEngineException[[informationObjects][BTRB3H7GNVGIDDTK5VLJHIL4VE]:
version conflict, current version [-1] is different than the one provided [15]]
```
I am pretty sure the document exists because actually, I fetched it before the update.
My ES version is 6.8.22 and the source code shows the error comes from `org.elasticsearch.index.engine.InternalEngine#index`.
Can anybody tell me what is the method for? And give me a little hint on why it is called.
It is a bug? Fixed in the later releases? Thanks!
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [August 4, 2022, 6:33am UTC](https://discuss.elastic.co/t/es-versionconflictengineexception-current-version-1/311282/2 "2022-08-04T06:33:23Z")
What does your node configuration look like? Do you have `minimum_master_nodes` correctly set to `2` so you avoid split brain scenarios given that you have 3 master-eligible nodes?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 1, 2022, 6:34am UTC](https://discuss.elastic.co/t/es-versionconflictengineexception-current-version-1/311282/3 "2022-09-01T06:34:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.