[SERVER-78499] Move overrideDDLLockTimeout failpoint under DDLLockManager implementation Created: 28/Jun/23 Updated: 29/Oct/23 Resolved: 18/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Silvia Surroca | Assignee: | Silvia Surroca |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21 |
| Participants: |
| Description |
|
The overrideDDLLockTimeout is a fail point created to decrease the DDL lock acquisition timeout in order to speed up some tests. However, not all the tests can use it because the fail point is only implemented when the DDL lock is acquired from a ShardingDDLCoordinator. The goal of this ticket is to move the {{overrideDDLLockTimeout }}fail point implementation under the DDLLockManager implementation. |
| Comments |
| Comment by Githook User [ 18/Aug/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |