Concurrent document create with _version

Elastic Stack Elasticsearch
1

Hi,

I'm using optimistic locking with the version field to avoid update anomalies. We also roll indexes in our cluster based on time/size.

I was wondering whether the unique _id and versioning constraints are maintained across indexes when accessed through an alias... Trying to track down the source of an update anomaly.

Thanks!

2

They are per shard. If you roll the index or use bad routing you can have
trouble.

3

We aren't using any custom routing. So if we don't roll this index, and just let it grow shards by itself, are we safe?