[SERVER-16722] Increase dropDatabase logging level for starting/finishing Created: 05/Jan/15  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Logging, Write Ops
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Scott Hernandez (Inactive) Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: commands, dropDatabase, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Participants:

 Description   

These should probably be level 1, not info as they are now.

2015-01-05T11:49:48.553-0500 I COMMAND  [conn3] dropDatabase <DB> starting
2015-01-05T11:49:48.554-0500 I COMMAND  [conn3] dropDatabase <DB> finished

It is questionable that we want something at default log level when a database is dropped since the time you care about this is for long running drops which will be logged anyway as a slow operation.


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