-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-07-31
renameCollection will fail if it would cause an index name to be too long. To avoid this, we will drop any problematic indexes and log an oplog entry for their drops before renaming the collection and logging the collection drop to the oplog. This will only apply to mmap as we will relax this constraint for wiredTiger and mmap rollback will seamlessly succeed since we already know how to rollback index drops.
- is duplicated by
-
SERVER-29748 Two Phase Drops: drop indexes with long names under mmap before doing collection renames
- Closed
- is related to
-
SERVER-31060 Two phase drops with too long MMAPv1 index names must generate dropIndexes operations before drop operation
- Closed
-
SERVER-29373 Two Phase Drops: Relax index namespace length constraint under non-mmapv1 storage engines when doing collection renames for two phase drops
- Closed
- related to
-
SERVER-31351 rolling back a collection drop with long index names may not restore all the indexes
- Closed
-
SERVER-29373 Two Phase Drops: Relax index namespace length constraint under non-mmapv1 storage engines when doing collection renames for two phase drops
- Closed
-
SERVER-32959 Remove index name length limit
- Closed