[SERVER-45145] Prevent merge_requires_unique_index.js and merge_with_move_primary.js from running in multiversion passthrough suites Created: 13/Dec/19  Updated: 29/Oct/23  Resolved: 12/Mar/20

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: sharding-4.4-stabilization, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Sharding 2020-03-23
Participants:
Linked BF Score: 49

 Description   

This test fails when the node targeted for the $merge is a v4.2 node, because making a shard node refresh on returning StaleDbVersion was added in v4.4. As a result, the node sending the $merge to the v4.2 keeps getting StaleDbVersion and keeps retrying until it runs out of retries, causing the test to fail.



 Comments   
Comment by Esha Maharishi (Inactive) [ 20/Apr/20 ]

Thanks steven.vannelli for following up. This doesn't need to go into master, and actually can be reverted on v4.4 once BF-16893 is fixed - we realized that this actually should be a supported combination and are going to put a fix into 4.4 to fix it.

Comment by Githook User [ 12/Mar/20 ]

Author:

{'username': 'BlakeIsBlake', 'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com'}

Message: SERVER-45145 Blacklist merge_requires_unique_index.js and merge_with_move_primary.js from sharding_multiversion suite
Branch: v4.4
https://github.com/mongodb/mongo/commit/2d300828d700533f77d1240714e3ccecdb6f1747

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