[SERVER-50462] sharding_rs2.js tries to send command to secondaries that can be stale Created: 21/Aug/20  Updated: 29/Oct/23  Resolved: 14/Sep/20

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-09-21
Participants:
Linked BF Score: 10

 Description   

Test starts as 2 node replica set shards, does a migration with _waitForDelete: true and tries to call count with slaveOk. Range deletion waits for majority and this would have been fine if there were only 2 nodes, but the test adds another at the beginning, so it has 3. This means that the count command could be sent to a node that has not yet replicated the orphan cleanup.

They were instances in the tests where it would wait for all nodes to catch up, but there was none for the latter half of the test.



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

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-50462: Have sharding_rs2 wait for replication to safely assert causal expectations.
Branch: master
https://github.com/mongodb/mongo/commit/e21416d2889b54830624d812a48b2a5e07f4e47a

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