Delete by query, what's the behavior of conflicts=proceed

Elastic Stack Elasticsearch
1

If I have two servers sending the same delete by query request to a single ES server all the time. Two deletion tasks will always conflict with each other. If I have conflicts=proceed, what will really happen? My guess is, both tasks will be completed with response
{total: 1000000, deleted: someNum, version_conflicts = 1000000 - someNum}
and the other with response
{total:1000000, deleted:1000000 - someNum, version_conflicts = someNum}.
Am I right? How does conflicts=proceed really work?

2

Don't close the topic!

3

I think you're right.

This option just tells elasticsearch that in case of conflict (ie a document is updated or deleted in the meantime) it will continue to process the other documents.