[SERVER-57134] Adjust resharding critical section timeout value Created: 21/May/21  Updated: 06/Dec/22  Resolved: 07/Jun/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Lamont Nelson Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Won't Do Votes: 0
Labels: PM-234-M3, PM-234-T-autocommits, post-rc0, sharding-product-sync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding NYC
Participants:
Story Points: 1

 Description   

Initial testing shows that we might be a bit too strict when deciding to move to blocking writes. We'll probably want to introduce additional time for the timeout value to account for variance in workload and system performance.

Exact values are not decided yet, but this is a placeholder for that discussion.



 Comments   
Comment by Max Hirschhorn [ 05/Jun/21 ]

lamont.nelson, given the changes from SERVER-57303, would you say an adjustment to resharding's critical section timeout value of 5 seconds is still needed?

Generated at Thu Feb 08 05:41:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.