[SERVER-44182] Blacklist major_version_check.js from sharding_last_stable suite in 3.6 Created: 23/Oct/19  Updated: 29/Oct/23  Resolved: 24/Oct/19

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

Type: Bug Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-11-04
Participants:
Linked BF Score: 37

 Description   

In 3.4, after running split chunk, shards always refresh their metadata, which would cause any command to that shard from the stale mongos to receive a stale config error (which is what happens). In contrast, in 3.6 and up, shards only refresh their metadata if split chunk fails for some reason, which is why major_version_check.js works. We should blacklist this test in the last stable suite.



 Comments   
Comment by Githook User [ 24/Oct/19 ]

Author:

{'username': 'saltzm', 'email': 'matthew.saltz@mongodb.com', 'name': 'Matthew Saltz'}

Message: SERVER-44182 Blacklist major_version_check.js from last stable suite
Branch: v3.6
https://github.com/mongodb/mongo/commit/dd297316e12bd92f3737424ac0b951e282de8e0d

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