[SERVER-85408] Use higher wtimeout in catalog_shard.js Created: 18/Jan/24 Updated: 23/Jan/24 Resolved: 23/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5 | ||||
| Participants: | |||||
| Linked BF Score: | 30 | ||||
| Description |
|
catalog_shard.js passes a wtimeout with the config shard transition commands to verify it accepts them, but uses a relatively small value - 100ms - which can be exceeded on slow platforms. We can keep the same coverage and avoid failures by using a much higher timeout, like 1 day. |
| Comments |
| Comment by Githook User [ 19/Jan/24 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: GitOrigin-RevId: f72464aa38a5c13e5a1a39e084e34e8b6de6b3c2 |