[SERVER-19034] log command failures at level 1 Created: 18/Jun/15  Updated: 05/Feb/16  Resolved: 18/Jun/15

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: 3.1.5

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Adam Midvidy
Resolution: Done Votes: 0
Labels: Fit&Finish
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platform 5 06/26/16
Participants:

 Description   

Currently in master, a new behavior is to log every command failure or assertion. This includes command parsing errors and every uassert that a command may throw. For example, the not-master assertion:

2015-06-18T13:47:18.401-0400 I COMMAND  [conn2] assertion while executing command 'getMore' on database 'test' with arguments '{ getMore: 62016858025, collection: "foo", term: 1 }' and metadata '{}': 13435 not master and slaveOk=false

I believe we should change this to log at debug log level 1, to avoid filling the server log with what are essentially user-generated common errors.



 Comments   
Comment by Githook User [ 18/Jun/15 ]

Author:

{u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}

Message: SERVER-19034 log command errors at log level 1
Branch: master
https://github.com/mongodb/mongo/commit/a0070b263ba180343a4dc1475c78c571178665c7

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