Profiler collection not created when using --profile

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Hide 
      var conn = MongoRunner.runMongod({profile: 2});
var t = conn.getDB('test').foo;

// this insert should trigger the creation of the profiler collection
t.insert({});

var colls = t.getDB().getCollectionNames();
assert.contains('system.profile', colls, tojson(colls));

MongoRunner.stopMongod(conn);
      Show
      var conn = MongoRunner.runMongod({profile: 2}); var t = conn.getDB('test').foo; // this insert should trigger the creation of the profiler collection t.insert({}); var colls = t.getDB().getCollectionNames(); assert.contains('system.profile', colls, tojson(colls)); MongoRunner.stopMongod(conn);
    • None
    • 3
    • 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" ]

            Assignee:
            Kaloian Manassiev
            Reporter:
            Kamran K. (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: