[DOCS-12553] Upgrade notes for 3.6 should include adjustment to settings.catchUpTimeoutMillis Created: 18/Mar/19 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | 3.6 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Steve Choi (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
DescriptionI believe the implementation for SERVER-26848 sets settings.catchUpTimeoutMillis to be infinite (-1) by default. In pre-3.6, the value cannot be a negative number, thus it was defaulted to either 2000 or 60000. The 4.0 upgrade notes mentions this setting to be increased to mitigate w:1 rollbacks. However, the 3.6 upgrade notes does not mention this setting at all. Therefore, customers upgrading from pre-3.6 to 3.6 will tend to have the 2000 or 60000 default values. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |