[DOCS-322] TTL collection background task for deleting documents every minute Created: 05/Jul/12  Updated: 30/Oct/23  Resolved: 12/Jul/12

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Stennie Steneker (Inactive) Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-6304 TTL collections not honoring strict t... Closed
Participants:
Days since reply: 11 years, 31 weeks, 6 days ago

 Description   

Per some enthusiastic investigation on SERVER-6304 and a closer reading of SERVER-211, I discovered that the documents in a TTL collection are deleted by a background task that runs once a minute.

This needs to be added/highlighted in the documentation as expireAfterSeconds won't be strictly honoured if less than 60 seconds:
http://docs.mongodb.org/manual/tutorial/expire-data/



 Comments   
Comment by auto [ 12/Jul/12 ]

Author:

{u'date': u'2012-07-12T07:58:12-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-322 adding notes about capped collections and TTL indexes
Branch: master
https://github.com/mongodb/docs/commit/ff2616d6e3c566887527b22ff2a435037ee12d6d

Comment by Kevin Matulef [ 12/Jul/12 ]

Sam, can you add a note in the "constraints" section of the TTL docs, to say that TTL indexes will not work with capped collections, since documents cannot be removed from them? (you can create a TTL index on a capped collection, but it will just throw an error every 60 seconds whenever the background task runs).

Comment by auto [ 05/Jul/12 ]

Author:

{u'date': u'2012-07-05T08:17:59-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-322 adding note about timing for TTL collections
Branch: master
https://github.com/mongodb/docs/commit/59ec4d488319743ca22b1037e0f392bc6c889fff

Generated at Thu Feb 08 07:38:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.