[SERVER-34019] Downgrade global snapshot reads Created: 20/Mar/18  Updated: 29/Oct/23  Resolved: 28/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: Misha Tyulenev 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   

Verify that during downgrade commands with readConcern level:snapshot are rejected.

Summary:

  • Verify that snapshot read concern is accepted when the cluster is fully upgraded, in both FCV 4.0 and 3.6, then disallowed as soon as mongos is downgraded and at every downgrade stage after.

Design:

  • Invert jstests/multiversion/global_snapshot_reads_upgrade_cluster.js to downgrade a cluster instead, and add assertions on the behavior of snapshot reads at each stage.


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

Author:

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

Message: SERVER-34019 Test global snapshot reads downgrade behavior
Branch: master
https://github.com/mongodb/mongo/commit/2e1542e518b6df660bb3a4c1ce0020c293b928b5

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