[SERVER-85192] Increase reshardingOplogApplierMaxLockRequestTimeoutMillis in Unit Tests Created: 12/Jan/24 Updated: 12/Jan/24 Resolved: 12/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brett Nawrocki | Assignee: | Brett Nawrocki |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Setting reshardingOplogApplierMaxLockRequestTimeoutMillis to 1ms is strict enough to fail consistently on my workstation. |
| Sprint: | Cluster Scalability 2024-1-22 |
| Participants: |
| Description |
|
ReshardingOplogApplicationRules, when trying to acquire a collection, uses a deadline based on reshardingOplogApplierMaxLockRequestTimeoutMillis, which defaults to 5ms. As seen in BF-30275, this is sometimes too strict for slower variants (e.g. debug, windows). The timeout should be increased during unit tests. |
| Comments |
| Comment by Brett Nawrocki [ 12/Jan/24 ] |
|
The semantics of the timeout need to be addressed via |