[SERVER-53571] Determine the best default timeout for tenant migration blocking phase Created: 05/Jan/21 Updated: 08/Nov/22 Resolved: 08/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Shuvalov (Inactive) | Assignee: | Matt Broadstone |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Sprint: | Server Serverless 2022-11-14 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
The code for the timeout is submitted in The IDL definition to configure the timeout is here: https://github.com/mongodb/mongo/blob/a102bde490e4f63a5558551f31e3c834edeb4dd6/src/mongo/db/repl/repl_server_parameters.idl#L426-L435 Most likely the timeout will be determined by experiments and beta deployment. It should be as large as needed to almost guarantee that the blocking phase will go through without timing out even when the server is overloaded, but it should not be too large, because it blocks reads/writes to the migrated database.
|
| Comments |
| Comment by Matt Broadstone [ 08/Nov/22 ] |
|
Closing WONTDO after committing the change to remove the TODO. |
| Comment by Githook User [ 08/Nov/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: |
| Comment by Steven Vannelli [ 31/Oct/22 ] |
|
Reopening so that we can make another commit to remove the TODO associated with it. |
| 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. |