[SERVER-12136] scanAndOrder doesn't appear in profiler output in 2.5.x Created: 17/Dec/13  Updated: 11/Jul/16  Resolved: 10/Jan/14

Status: Closed
Project: Core Server
Component/s: Diagnostics, Querying
Affects Version/s: 2.5.4
Fix Version/s: 2.5.5

Type: Bug Priority: Minor - P4
Reporter: Sam Kleinman (Inactive) Assignee: David Storch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-10566 performance pass: idhack, findingStar... Closed
is depended on by DOCS-2418 Comment on: "manual/reference/databas... Closed
Participants:

 Description   

db.setProfilingLevel(0)
db.system.profile.drop()
db.bar.drop();
 
db.bar.insert( { "x" : 7, "r" : 0.999768219422549 } )
db.bar.insert( { "x" : 92, "r" : 0.9881451367400587 } )
db.bar.insert( { "x" : 45, "r" : 0.9833264029584825 } )
 
// no indexes other than { _id: 1 } 
 
db.setProfilingLevel(2)
 
db.bar.find().sort( { r: -1 } )
 
db.system.profile.find().sort( {$natural: 1} ).limit(1).pretty();

In 2.4.x we see a document that has the scanAndOrder field which doesn't appear in 2.5.5-pre.

Previously scanAndOrder only appeared when true, which is itself a bit odd.



 Comments   
Comment by Githook User [ 13/Jan/14 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-12136 fix explain asserts

Signed-off-by: Matt Kangas <matt.kangas@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/32646abb0b93eee036739d9e48a13c88d5956cc0

Comment by Githook User [ 10/Jan/14 ]

Author:

{u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}

Message: SERVER-12136 don't error if explain for profiler fails
Branch: master
https://github.com/mongodb/mongo/commit/1d84ad9a0b48e1707d90196c5b6d60d33af58525

Comment by Githook User [ 10/Jan/14 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-12136 hook additional profiler fields up to the query system

Signed-off-by: Matt Kangas <matt.kangas@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/0abcd25376977c3f63db11446ab0b18c0ce88fff

Comment by Daniel Pasette (Inactive) [ 17/Dec/13 ]

This depends on SERVER-10566.

jstests/profile4.js which checks is disabled until then.

Generated at Thu Feb 08 03:27:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.