[SERVER-31109] race in multi_mongos2.js can cause count to be targetted to wrong shard Created: 15/Sep/17  Updated: 27/Oct/23  Resolved: 19/Nov/19

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Gone away Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Sprint: Sharding 2019-12-02
Participants:
Linked BF Score: 0

 Description   

Setup: 2 mongos, 2 shards.

1. movePrimary sent to mongos1.
2. movePrimary changed primary from shardA to shardB
3. send insert to mongos1.
4. send count to mongos2. Mongos2 still sees state before movePrimary and routes count to shardA.
5. shard does not reject count since version matches (0,0|0) matches (0,0|0)
6. counts shows 0 documents.



 Comments   
Comment by Randolph Tan [ 19/Nov/19 ]

This should no longer be an issue thanks to PM-1017

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