Starting in 5.0, the 'weights' field became a reserved field for text indexes. This is an issue for deployments that were upgraded from older versions to 5.0+, because they may still have non-text indexes with this 'weights' field.
This causes mongosync processes syncing data from a source cluster with the above to error out because mongosync tries to re-create the same indexes on the destination cluster that's on MongoDB 5.0. mongosync uses the ignoreUnknownIndexOptions when creating indexes, which avoids most instances of invalid index fields but this did not work for the 'weights' field (see reproduction notes below).
- causes
-
SERVER-84434 Chunk migration may fail due to indexes having not relevant and invalid index options
- Closed
- is caused by
-
SERVER-65797 Remove invalid index specs in memory before parsing for listIndexes
- Closed
- is related to
-
SERVER-79645 Make CheckReplDBHash accept multi-version index spec mismatch
- Closed