[SERVER-6712] Make TTL Collection background task period user defined (command line option) Created: 04/Aug/12 Updated: 06/Dec/22 Resolved: 14/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | TTL, Usability |
| Affects Version/s: | 2.2.0-rc0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Pieter Willem Jordaan | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 3 |
| Labels: | collection, indexes, ttl | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
N/A |
||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
TTL collections are a great way to implement a heartbeat/failover monitor. But the fixed time background task makes this a bit slow. Could it be made possible to adjust this background task's period? It might even be useful to have seperate tasks, one per TTL collection. |
| Comments |
| Comment by Connie Chen [ 14/Mar/22 ] |
|
We do want to make TTL deletes less impactful, but we do not think the command line solution is the correct method. There is also an existing server parameter that can address those specific use cases that require this. |
| Comment by Mehdi Haddoun [ 18/Sep/14 ] |
|
+1 vote for this issue |
| Comment by Johan Hedin [ 01/May/13 ] |
|
+1 on this one. Our case is different though. When you use the TTL on a collection that has a high sustained insert rate and a lot of indexes (like many hundreds inserts per second and ten indexes), doing TTL removes once every minute seem to put more stress on the system than removing more often. Our own external TTL implementation runs constantly and thus even out the load. |