[DOCS-15908] [SERVER] Server parameter docs for range deletion parameters pre 6.0 should advise forced step down Created: 17/Feb/23 Updated: 30/Oct/23 Resolved: 28/Jul/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | 4.4.0, 4.4.2, 5.0.0, 6.0.0, 6.1.0, 6.2.0 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Allison Easton | Assignee: | Anika Malhotra (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | proactive, quick-win, server-docs-bug-bash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 36 weeks ago | ||||
| Description |
|
The server parameters docs for orphanCleanupDelaySecs should mention that in all versions, the new value is only applied to range deletions created after the value is changed and that in order for the new value to be applied to existing range deletions the user should force a step down. The server parameters docs for rangeDeleterBatchDelayMS, and rangeDeleterBatchSize should mention that in versions prior to 6.0.3, the new value is only applied to range deletions created after the value is changed and that in order for the new value to be applied to existing range deletions, the user should force a step down. |
| Comments |
| Comment by Ashley Brown [ 31/May/23 ] |
|
Bumping priority due to linked HELP ticket. |