# seqNo generation strategy - seqNo question

**URL:** <https://discuss.elastic.co/t/seqno-generation-strategy-seqno-question/336027>\
**Category:** Elasticsearch\
**Created:** [June 15, 2023, 2:06am UTC](https://discuss.elastic.co/t/seqno-generation-strategy-seqno-question/336027 "2023-06-15T02:06:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SnowFlakeLeaf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/snowflakeleaf/32/122262_2.png) [@SnowFlakeLeaf](https://discuss.elastic.co/u/SnowFlakeLeaf)\
**Post date:** [June 15, 2023, 2:06am UTC](https://discuss.elastic.co/t/seqno-generation-strategy-seqno-question/336027/1 "2023-06-15T02:06:24Z")

</div>

The source of the problem is that we request in multiple concurrent modification in production in a lot of the same document VersionConflictEngineException, And we didn't include if\_seq\_no in the request, so we wanted to explore the details of the seqNo generation strategy and version control on the server side of elasticsSearch.  
In the 7.10 source code we only find that the seqNo of the current document is obtained before it is actually added or updated, but we do not find how the seqNo value for the new request is generated.  
We are using version 7.10.  
Thank you very much in advance.

---

<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 13, 2023, 2:07am UTC](https://discuss.elastic.co/t/seqno-generation-strategy-seqno-question/336027/2 "2023-07-13T02:07:19Z")

</div>

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