Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
2.10.1
-
None
-
None
-
linux 64 bit with --keyfile option
Description
When reading the profiling status, profiling will be disabled afterwards.
Reproduce:
Turn on profiling: db.setProfilingLevel(1,3000)
PRIMARY> db.setProfilingLevel(1,3000)
Execute Java code to read out status:
final CommandResult cr = offerStoreDb.command("profile");
|
or even:
DBObject command = new BasicDBObject();
|
command.put("profile", "1");//may be -1 as well
|
final CommandResult cr = offerStoreDb.command(command);
|
When re-checking in console, profiling is OFF:
PRIMARY> db.getProfilingLevel()
0