Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Execution Team 2024-04-01, Execution Team 2024-04-15
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Vishnu Kaushik
Reporter:: Vishnu Kaushik
Participants:: Githook User, Vishnu Kaushik
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Mar 25 2024 07:38:39 PM UTC
Updated:: Apr 01 2024 09:30:02 PM UTC
Resolved:: Apr 01 2024 09:16:47 PM UTC
Confidence Status Last Update:: 26/Mar/24 2:47 PM