[SERVER-48658] The TTL monitor should not log at "E" level for QueryPlanKilled Created: 08/Jun/20  Updated: 29/Oct/23  Resolved: 07/Jul/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.4.1, 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Geert Bosch Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Execution Team 2020-06-29, Execution Team 2020-07-13
Participants:
Linked BF Score: 0

 Description   

It is expected that a collection drop can kill a query plan while the TTL monitor is deleting old document, and this is not an error. I see three ways we could address this:

  • Log at level W (warning)
  • Log at level I (informational)
  • Just catch/ignore the exception for QueryPlanKilled and not log anything.

I lean toward the last option.



 Comments   
Comment by Githook User [ 21/Aug/20 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-48658 Stop logging QueryPlanKilled error in TTL monitor

(cherry picked from commit c0c6890f477a9faa239dada415259fe57a2c6d7b)
Branch: v4.4
https://github.com/mongodb/mongo/commit/cfbde7b91048af890fc1fa7ad47e154f336d6d9c

Comment by Githook User [ 07/Jul/20 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-48658 Stop logging QueryPlanKilled error in TTL monitor
Branch: master
https://github.com/mongodb/mongo/commit/c0c6890f477a9faa239dada415259fe57a2c6d7b

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