[SERVER-70055] Use new TTL sleep config immediately after set Created: 28/Sep/22 Updated: 29/Oct/23 Resolved: 15/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Jordi Olivares Provencio |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | michael-preferred | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2023-03-20 |
| Participants: |
| Description |
|
The TTL performs a sleep of the amount of seconds configured before waking up and performing a pass. This causes new config changes to only be picked up after the previous amount of seconds have passed. This opens up the possibility of a TTL being erroneously set to a very large number of seconds and be unable to fix it unless you wait or restart the server with the new settings. In other words: if I start the server and change the TTL monitor sleep seconds from 60 to 1 the server will still wait the full 60 seconds after setting the value before using 1. |
| Comments |
| Comment by Githook User [ 14/Mar/23 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |