[SERVER-41078] Make replica set primary detection stepdown-proof in concurrency workloads Created: 09/May/19  Updated: 29/Oct/23  Resolved: 14/May/19

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

Type: Bug Priority: Major - P3
Reporter: Blake Oler Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-39844 Create concurrency workload with migr... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-05-20
Participants:

 Description   

The chunks helper for concurrency workloads has a function to retrieve the primary replica set node from a shard.

If this function doesn't find a primary node from any of the current nodes, it returns immediately. This is not stepdown-proof, as a node could be transitioning to primary but not yet reporting isMaster: true.

We should use assert.soon with a short-ish timeout instead of immediately returning and failing a test, similar to what the replica set test class does.



 Comments   
Comment by Githook User [ 14/May/19 ]

Author:

{'email': 'golden.janna@gmail.com', 'name': 'jannaerin', 'username': 'jannaerin'}

Message: SERVER-41078 Make replica set primary detection stepdown-proof in concurrency workloads
Branch: master
https://github.com/mongodb/mongo/commit/cd651e5e12eb5416883776ced095805bc585e8bc

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