[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: |
|
||||||||||||||||
| 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 |