[SERVER-81426] [5.0] fsync_deadlock.js is not resilient to StaleConfig errors Created: 25/Sep/23  Updated: 29/Oct/23  Resolved: 27/Sep/23

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

Type: Bug Priority: Major - P3
Reporter: Nandini Bhartiya Assignee: Nandini Bhartiya
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
Participants:
Linked BF Score: 147

 Description   

Force the recipient shard to refresh its routing table for the collection to ensure the transaction is not implicitly aborted when running fsync_deadlock.js in mixed version test suites (v6.0 & v5.0).

Improvements were made to chunk migration such that refreshing the routing cache forcefully was not needed in 6.0+.



 Comments   
Comment by Githook User [ 26/Sep/23 ]

Author:

{'name': 'Nandini Bhartiya', 'email': 'nandini.bhartiya@mongodb.com', 'username': 'nandinibhartiyaMDB'}

Message: SERVER-81426 : Fix multiversion test failure
Branch: v6.0
https://github.com/mongodb/mongo/commit/7373aa3d7e056ccf921cd26689787e7c06cfac08

Generated at Thu Feb 08 06:46:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.