Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-36717

profile command returns that it can only be run from admin database

XMLWordPrintableJSON

    • Cluster Scalability
    • ALL
    • Hide

      ./scratch/setprof.js:
      ```
      (function() {
      assert.commandWorked(db.test.insert({}));
      assert.commandWorked(db.setProfilingLevel(2));
      })();
      ```

      buildscripts/resmoke.py --suites=sharding_jscore_op_query_passthrough ./scratch/setprof.js

      Show
      ./scratch/setprof.js: ``` (function() { assert.commandWorked(db.test.insert({})); assert.commandWorked(db.setProfilingLevel(2)); })(); ``` buildscripts/resmoke.py --suites=sharding_jscore_op_query_passthrough ./scratch/setprof.js
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When running in sharding_jscore_op_query_passthrough, a jstest that calls setProfilingLevel is returned an errmsg: " profile may only be run against the admin database.".

      Error because profile does not need to be run on admin database.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            ben.judd Ben Judd (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: