-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 2.8.0-rc5
-
Component/s: Diagnostics, Storage
-
Fully Compatible
-
ALL
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Starting with commit 02a78a7f3 (from SERVER-16431), a system.profile collection is no longer created when using --profile. The collection is still created when enabling the profiler via runCommand, however:
// Using `./mongod --profile=2` // > db.runCommand({profile: 2}); { "was" : 2, "slowms" : 100, "ok" : 1 } > db.getCollectionNames(); [ "system.indexes" ] > db.foo.insert({}); WriteResult({ "nInserted" : 1 }) > db.getCollectionNames(); [ "foo", "system.indexes" ] // Using `./mongod` // > db.runCommand({profile: 2}); { "was" : 0, "slowms" : 100, "ok" : 1 } > db.getCollectionNames(); [ "system.indexes", "system.profile" ] > db.foo.insert({}); WriteResult({ "nInserted" : 1 }) > db.getCollectionNames(); [ "foo", "system.indexes", "system.profile" ]