-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:
*Location*: http://docs.mongodb.org/manual/core/journaling/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.71 Safari/537.36
*Referrer*: https://www.google.com/
*Screen Resolution*: 1920 x 1200
*repo*: docs
*source*: core/journaling
*Location*: http://docs.mongodb.org/manual/core/journaling/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.71 Safari/537.36 *Referrer*: https://www.google.com/ *Screen Resolution*: 1920 x 1200 *repo*: docs *source*: core/journaling
"Bug" in the code... 
"Note Depending on your file system, you might experience a preallocation lag the first time you start a mongod instance with journaling enabled. MongoDB preallocates journal files if it is faster on your file system to create files of a pre-defined. The amount of time required to pre-allocate lag might last several minutes, during which you will not be able to connect to the database. This is a one-time preallocation and does not occur with future invocations."
1.) We have an incomplete sentence there, and it doesn't really make sense.
2.) We don't explain how MongoDB determines this; is it specific hard-coded filesystems, or does it try and then make a decision based on that, or...?
Thanks,
Nicholas