-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
-
Fully Compatible
-
ALL
Since we copy the data from different snapshots and start building indexes before cloning data. The index spec may be inconsistent with the copied data, causing idempotency issues.
Creat geo index --- start clone, get the geo index --- Drop the geo index Insert an invalid geo document --- copy the data, triggering geo parsing errors ----
Relaxing index constraints in data cloning is one possible solution.
- duplicates
-
SERVER-26202 Relax index constraints in oplog application
- Closed