[SERVER-61924] retryable_mongos_write_errors.js fails in 4.2 multiversion suites due to missing failpoint command in 4.0 Created: 06/Dec/21  Updated: 29/Oct/23  Resolved: 09/Dec/21

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

Type: Bug Priority: Major - P3
Reporter: Luis Osta (Inactive) Assignee: Luis Osta (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-12-27
Participants:
Linked BF Score: 15
Story Points: 2

 Description   

Example of failure - https://evergreen.mongodb.com/task/mongodb_mongo_v4.2_enterprise_rhel_62_64_bit_display_sharding_last_stable_mongos_and_mixed_shards_c797110b90fd5d950fa5d78aa26ae198c76883c6_21_12_03_21_30_06

How It Happens:

  • The tests are running on a mixed cluster (my guess is 4.2 something and 4.0 something)
  • The 4.2 test uses the failpoints introduced in 4.2
  • The 4.0 server code does not have the wait for failpoint command (just searched), so that when the 4.2 test uses the failpoint helpers to execute the failpoint commands, it will fail Because the 4.0 shards don't have those command


 Comments   
Comment by Githook User [ 09/Dec/21 ]

Author:

{'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}

Message: SERVER-61924 Replace test with the v4.0 version due to missing failpoint commands
Branch: v4.2
https://github.com/mongodb/mongo/commit/0ff3674221b15c471ee5c5dae8f81c4365cb16e0

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