[SERVER-60556] Migration recipient timeout for range deletion is too short on the sharding_update_v1_oplog suite Created: 08/Oct/21 Updated: 29/Oct/23 Resolved: 11/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding EMEA
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding EMEA 2021-10-18 | ||||
| Participants: | |||||
| Linked BF Score: | 57 | ||||
| Description |
|
The default timeout for waiting for range deletions is 10 seconds, in some suites like concurrency_sharded_replication is 90 seconds, we need to increase the default for the sharding_update_v1_oplog suite. |
| Comments |
| Comment by Githook User [ 11/Oct/21 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |