-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
Execution Team 2024-04-01, Execution Team 2024-04-15
As a temporary solution before SERVER-88375 goes in, use the idiom here to ensure that the _nextIdNum value in the record store is updated by secondaries / initial syncing nodes as they perform inserts.
SERVER-88375 is expected to provide a long-term solution, where we may extract the recordId tracking to a higher level.
- is related to
-
SERVER-88375 Initial sync / secondary oplog application don't update _nextId for recordId
- Open
-
SERVER-88816 Break up WiredTigerRecordStore::_insertRecords()
- Backlog