-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Critical - P2
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Minor Change
-
ALL
-
-
Server 2.7.4, Server 2.7.5, Server 2.7.6
Mac OSX, starting up mongod from commend line (either no parameters, or passing an empty config file (old format)), using a new db and inserting inserting a single document.
In 2.6.3, I get the following:
drwxr-xr-x 2 thomasboyd wheel 68 Jul 16 15:03 _tmp drwxr-xr-x 3 thomasboyd wheel 102 Jul 16 15:02 journal -rw------- 1 thomasboyd wheel 67108864 Jul 16 15:03 local.0 -rw------- 1 thomasboyd wheel 16777216 Jul 16 15:03 local.ns -rwxr-xr-x 1 thomasboyd wheel 5 Jul 16 15:02 mongod.lock -rw------- 1 thomasboyd wheel 67108864 Jul 16 14:50 test.0 -rw------- 1 thomasboyd wheel 16777216 Jul 16 14:50 test.ns
In 2.4.10, I get the following (note two data files for test DB):
drwxr-xr-x 2 thomasboyd wheel 68 Jul 16 14:57 _tmp drwxr-xr-x 2 thomasboyd wheel 68 Jul 16 15:01 journal -rw------- 1 thomasboyd wheel 67108864 Jul 16 14:57 local.0 -rw------- 1 thomasboyd wheel 16777216 Jul 16 14:57 local.ns -rwxr-xr-x 1 thomasboyd wheel 0 Jul 16 15:01 mongod.lock -rw------- 1 thomasboyd wheel 67108864 Jul 16 14:57 test.0 -rw------- 1 thomasboyd wheel 134217728 Jul 16 14:57 test.1 -rw------- 1 thomasboyd wheel 16777216 Jul 16 14:57 test.ns
Other than for changes around the way no/prealloc is set in YAML files, I could not find any explanation for this change of behavior in release notes or jira tickets.
- is related to
-
SERVER-13508 Don't ignore --nopreallocj if there are already prealloced files
-
- Closed
-
-
SERVER-12644 Move note about noprealloc hurting performance to startup warnings
-
- Closed
-
- related to
-
-
- Closed
-
- links to
