[SERVER-20083] Add log statement at default log level for when an index filter is set or cleared successfully Created: 21/Aug/15  Updated: 17/Nov/16  Resolved: 29/Dec/15

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 2.6.12, 3.0.9, 3.2.3, 3.3.0

Type: Improvement Priority: Major - P3
Reporter: David Storch Assignee: James Wahlin
Resolution: Done Votes: 0
Labels: code-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: QuInt E (01/11/16)
Participants:

 Description   

For users with index filters, the performance of the application can rely on the index filters being set correctly. Currently, setting an index filter using the planCacheSetFilter command will only be logged if the slowms threshold is exceeded or if the logLevel is greater than 0. Logging these events would be useful both as a sanity check that the correct filter was applied and for postmortem analysis in the case that queries using index filters experience plan selection problems. Setting an index filter should be a rare event and therefore should not have any significant impact on the verbosity of logLevel 0 log files.



 Comments   
Comment by Githook User [ 11/Jan/16 ]

Author:

{u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}

Message: SERVER-20083 Log index filter change at default level

(cherry picked from commit dbd58e06914b23ed50605820515f3849baf2cbce)
Branch: v3.2
https://github.com/mongodb/mongo/commit/8764f93fd1bbafa18c83a2f926b420d8ad97a677

Comment by Githook User [ 04/Jan/16 ]

Author:

{u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}

Message: SERVER-20083 Log index filter change at default level

(cherry picked from commit dbd58e06914b23ed50605820515f3849baf2cbce)
Branch: v2.6
https://github.com/mongodb/mongo/commit/2f22fa93d4935ad9091264acf331f9a02d02954b

Comment by Githook User [ 30/Dec/15 ]

Author:

{u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}

Message: SERVER-20083 Log index filter change at default level

(cherry picked from commit dbd58e06914b23ed50605820515f3849baf2cbce)
Branch: v3.0
https://github.com/mongodb/mongo/commit/066f12fd7dd801114d08c4c25b6683aa4653408f

Comment by Githook User [ 29/Dec/15 ]

Author:

{u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}

Message: SERVER-20083 Log index filter change at default level
Branch: master
https://github.com/mongodb/mongo/commit/dbd58e06914b23ed50605820515f3849baf2cbce

Comment by James Wahlin [ 21/Aug/15 ]

Let's log planCacheClearFilters calls at logLevel 0 as well.

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