[SERVER-86161] Speed up accesses of oplogTruncateAfterPoint document Created: 02/Feb/24 Updated: 05/Feb/24 Resolved: 05/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The RecordId of the oplogTruncateAfterPoint document will never change during steady-state replication, but we constantly use the _id index to read and update the document. We could cache the RecordId to speed up reads and writes. Or we could cluster the collection, but that would need to consider possibly backward-breaking changes that would prevent downgrade. |