-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.0-rc4
-
Component/s: Index Maintenance, Replication
-
Replication
-
(copied to CRM)
-
0
For each known index idempotency problem, return a unique error to initial sync so that it can discern them and restart initial sync without failing tests. This will permit initial sync to detect unknown idempotency problems and fail tests rather than silently hide the problems.
ORIGINAL DESCRIPTION:
There are a number of additional index operations that should be idempotent and currently not handled by the improvements in SERVER-26202.
Applying the following operations on a collection before and after dropping it will cause initial sync to restart. They were found by going through the various checks in IndexCatalog::_doesSpecConflictWithExisting
1. creating indexes with different specs but the same name.
2. creating text indexes with different specs.
3. having more than 64 indexes combined, before and after dropping a collection.
- is depended on by
-
SERVER-33946 Decrease number of initial sync attempts in tests to 1
- Blocked
- is duplicated by
-
SERVER-33057 Indexing fatal assertion on secondary during sync
- Closed
- related to
-
SERVER-27357 Recreating collection with different collation during collection cloning phase can causes initial sync attempt to fail
- Backlog
-
SERVER-32225 Initial sync should ignore multiple text indexes on same collection error
- Closed
-
SERVER-44462 Run listIndexes with a single snapshot during initial sync
- Closed