Is it possible to have duplicate _id in a shard zone?

Hi Everyone,

Is it possible to have multiple documents with same _id field in a sharded mongodb environment with zones.

Consider below configuration :

Shard1 - ZoneA
Shard2 - ZoneA
Shard3 - ZoneB
Shard4 - ZoneB

Can i insert 2 docs with same _id into ZoneA / ZoneB ?

_id is primary and autogenerated. You can create a custom column abc_id and zone_id and then shared it.

Welcome to the community @nithin_reddy!

The technical possibility depends on your shard key index rather than zoning, but this is a scenario you definitely want to avoid.

The _id field uniquely identifies a document within a given collection on a shard. If documents have the same _id values on different shards, attempted migration of those documents to the same shard will result in a duplicate key exception. Non-unique _id values are also likely to lead to logic errors for developers or tools assuming _id is a unique identifier.

If your _id values are using default ObjectIDs, the chance of collision should be extremely low. However, if you are setting custom _id values and sharding without using _id as the shard key or a prefix of the shard key, you need to guard against the possibility of creating duplicate _id values.

This behaviour is described in the documentation on Sharded Clusters and Unique Indexes:

If the _id field is not the shard key or the prefix of the shard key, _id index only enforces the uniqueness constraint per shard and not across shards.

For example, consider a sharded collection (with shard key {x: 1} ) that spans two shards A and B. Because the _id key is not part of the shard key, the collection could have a document with _id value 1 in shard A and another document with _id value 1 in shard B.

If the _id field is not the shard key nor the prefix of the shard key, MongoDB expects applications to enforce the uniqueness of the _id values across the shards.


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