# \_version number incremented, but updates not reflected

**URL:** <https://discuss.elastic.co/t/version-number-incremented-but-updates-not-reflected/192081>\
**Category:** Elasticsearch\
**Created:** [July 24, 2019, 3:53pm UTC](https://discuss.elastic.co/t/version-number-incremented-but-updates-not-reflected/192081 "2019-07-24T15:53:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![calmel](https://avatars.discourse-cdn.com/v4/letter/c/a587f6/32.png) [@calmel](https://discuss.elastic.co/u/calmel)\
**Post date:** [July 24, 2019, 3:53pm UTC](https://discuss.elastic.co/t/version-number-incremented-but-updates-not-reflected/192081/1 "2019-07-24T15:53:10Z")

</div>

We have came across a weird situation where we see the \_version number incremented, but the actual document is not updated at all. We noticed that for said failed writes, the \_version number is higher than usual (we normally see \_version = 3, but for failure cases we see it go up to 4 or 5)

To allow us to further analyze the issue, we would like to know if \_version is incremented only by external write requests? Or does internal retries trigger an increment to the \_version number as well?

---

<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 21, 2019, 3:53pm UTC](https://discuss.elastic.co/t/version-number-incremented-but-updates-not-reflected/192081/2 "2019-08-21T15:53:23Z")

</div>

Closed on August 21, 2019, 3:53pm UTC

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