Details
-
Bug
-
Resolution: Won't Do
-
Major - P3
-
None
-
MongoDB: 3.2.4, OS X El Capitan 10.11
*Location*: https://docs.mongodb.org/manual/tutorial/expire-data/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Firefox/45.0
*Referrer*: https://www.google.com
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: tutorial/expire-data
MongoDB: 3.2.4, OS X El Capitan 10.11 *Location*: https://docs.mongodb.org/manual/tutorial/expire-data/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Firefox/45.0 *Referrer*: https://www.google.com *Screen Resolution*: 1440 x 900 *repo*: docs *source*: tutorial/expire-data
Description
Although you have an expireAfterSeconds parameter, it should be mentioned that it is not an exact timing system. For instance, if I put expireAfterSeconds=5, the document wouldn't actually be removed until 60 seconds later when mongod polls the index - at least, that's what happens on my system.