[SERVER-6374] Make TTL collections respect a hard limit instead of a soft minimum 60 seconds limit Created: 10/Jul/12 Updated: 06/Dec/22 Resolved: 19/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.1.2 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Christian Amor Kvalheim | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
Currently TTL collections are cleaned every 60 seconds. It would be good if the < 60 seconds expire time would be honored by offering a harder guarantee for removal than the current background job running every 60 seconds. |
| Comments |
| Comment by Christian Amor Kvalheim [ 10/Jul/12 ] |
|
very good point and that might be a much easier fix than doing the other thing. |
| Comment by Scott Hernandez (Inactive) [ 10/Jul/12 ] |
|
Might be easier to provide this behavior by simply not returning documents which exceed the ttl by filtering in the cursor (on the server). The main issue here is probably the returned data, not the deleting of the data. |