[SERVER-35534] unblacklist the database_versioning.js workload from the concurrency stepdown suites Created: 11/Jun/18  Updated: 09/Apr/20  Resolved: 24/Oct/19

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Won't Fix Votes: 0
Labels: open_todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-44241 Complete TODO listed in SERVER-35534 Closed
Sprint: Sharding 2018-06-18, Sharding 2018-07-02, Sharding 2018-07-16
Participants:

 Description   

It currently fails with PooledConnectionsDropped when setFCV is run concurrently with movePrimary.

It seems like it's due to a race condition in between creating a connection between the donor and recipient shards and tagging the connection as kKeepOpen in the NetworkInterfaceTL (so that setFCV does not close the connection with the non-retryable error code PooledConnectionsDropped).

This ticket is to finish investigating the root cause and either unblacklist the workload or update the comment in the places where it is blacklisted.



 Comments   
Comment by Githook User [ 09/Apr/20 ]

Author:

{'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}

Message: SERVER-44241 Complete TODO listed in SERVER-35534
Branch: master
https://github.com/mongodb/mongo/commit/f8cf1b50f90619c8f5abaad864b1a27dacf82b44

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