[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: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2019-12-02 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Setup: 2 mongos, 2 shards. 1. movePrimary sent to mongos1. |
| Comments |
| Comment by Randolph Tan [ 19/Nov/19 ] |
|
This should no longer be an issue thanks to PM-1017 |