-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
1
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
SERVER-62065 was a bug that caused chunks to have an empty 'history' array. SERVER-62065 also states that some old backup/restore procedures could have omitted restoring the 'history' array as well. Missing the 'history' causes transactions/snapshotReads to fail. As a result of this, the repairShardedCollectionChunksHistory was introduced.
It would be good to add a check to checkMetadataConsistency to ensure that clusters don't have a missing 'history' anymore.
- has to be done before
-
SERVER-104976 Deprecate the repairShardedCollectionChunksHistory command
-
- Closed
-
- is related to
-
SERVER-62065 Upgrade path from 3.6 to 4.0 can leave chunk entries without history on the shards
-
- Closed
-
- related to
-
-
- Closed
-