[SERVER-56302] Catalog cache refresh can fail with SnapshotTooOld after query yields Created: 23/Apr/21  Updated: 29/Oct/23  Resolved: 19/May/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 5.0.0
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-0-Metadata-Format
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-47855 Change default value for minSnapshotH... Closed
Related
is related to SERVER-54874 Ensure reading of consistent config.c... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 47

 Description   

The catalog cache refresh aggregation is executed with SnapshotReadConcern. If the query yields and the oldest_timestamp advances in the middle of the query, then the catalog cache refresh can fail with SnapshotTooOld. This is made worse by the fact that currently the minSnapshotHistoryWindow is only 5 seconds.



 Comments   
Comment by Jordi Serra Torrens [ 19/May/21 ]

Closing as SERVER-47855 has increased the minSnapshotHistoryWindow to 5 minutes.

Generated at Thu Feb 08 05:38:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.