seqNo generation strategy - seqNo question

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.

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