[SERVER-34182] Retry SnapshotTooOld errors in multiversion tests for global snapshot reads Created: 28/Mar/18  Updated: 29/Oct/23  Resolved: 29/Mar/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-04-09
Participants:

 Description   

Currently, the upgrade / downgrade tests for global snapshot reads introduced in SERVER-34019 and SERVER-34020 ignore SnapshotTooOld errors when expecting global snapshot reads to succeed. Those errors are somewhat acceptable, because they mean the read couldn't establish a snapshot, not that the attempt to do so was rejected. In 4.0 especially, the window for atClusterTime reads is very small and noop writes forced when the node hasn't reached the requested atClusterTime often advance the oldest timestamp beyond the requested time (see comments in readConcern_atClusterTime_noop_write.js, so repeated snapshot errors are likely.

The test should eventually be able to establish a snapshot for all reads though with enough attempts, so a retry loop should be added for the reads expected to succeed.



 Comments   
Comment by Githook User [ 29/Mar/18 ]

Author:

{'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'}

Message: SERVER-34182 Retry SnapshotTooOld errors in multiversion tests for global snapshot reads
Branch: master
https://github.com/mongodb/mongo/commit/edf4ceacfc64e53704614131dadeb0d12d7ebabf

Generated at Thu Feb 08 04:35:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.