[SERVER-82256] Account for the time mongos takes to update config server Created: 17/Oct/23 Updated: 29/Oct/23 Resolved: 19/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kruti Shah | Assignee: | Kruti Shah |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding NYC
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding NYC 2023-10-16 | ||||
| Participants: | |||||
| Linked BF Score: | 35 | ||||
| Description |
|
In repl_monitor_refresh.js, we start a sharding test with 1 shard that specifies 3 nodes. With auto-bootstrap, there is an auto initialization in the beginning which makes it necessary to be a reconfig when there are particular setting specified(like number of nodes). Mongos needs to update the config server on a topology state change so change the assert here to be an assert.soon in the case that mongos is a bit slow triggering the update. |
| Comments |
| Comment by Githook User [ 19/Oct/23 ] |
|
Author: {'name': 'Kruti Shah', 'email': 'kruti.shah@mongodb.com', 'username': 'krutishah139'}Message: |