[SERVER-70571] Choose a reasonable default value for shardSplitTimeoutMS Created: 14/Oct/22 Updated: 29/Oct/23 Resolved: 24/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Matt Broadstone |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Server Serverless 2022-10-31 | ||||
| Participants: | |||||
| Linked BF Score: | 45 | ||||
| Description |
|
We currently default this to one hour, which is probably unacceptable. Since this governs the critical section, and thus is tied directly to user perceived query latency, it should probably be a much smaller value. |
| Comments |
| Comment by Githook User [ 24/Oct/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: |
| Comment by Matt Broadstone [ 18/Oct/22 ] |
|
Re-opening because we just ran into a BF where this caused an issue. Setting this and tenantMigrationBlockingStateTimeoutMS ( |
| Comment by Matt Broadstone [ 18/Oct/22 ] |
|
Confirmed with cloud that this value will always be overridden, and they are not concerned about cases where it might not have been overridden. |