[SERVER-27038] assertion messages should have correct severities Created: 15/Nov/16  Updated: 06/Dec/17  Resolved: 09/Jun/17

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 3.5.9

Type: Task Priority: Major - P3
Reporter: Eric Milkie Assignee: Ted Tuckman
Resolution: Done Votes: 0
Labels: neweng, platforms-interns-2017
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-27850 Fatal assertions should have a higher... Closed
Related
related to SERVER-21201 Increase logging severity for Asserti... Closed
Backwards Compatibility: Fully Compatible
Sprint: Platforms 2017-06-19
Participants:

 Description   

For example, the fassert* family and invariant* family of functions should be calling severe(), not log().
msgasserted* family should be error(), as well as verifyFailed().



 Comments   
Comment by Githook User [ 09/Jun/17 ]

Author:

{u'username': u'TedTuckman', u'name': u'TedTuckman', u'email': u'ted.tuckman@mongodb.com'}

Message: SERVER-27038 changed assertion severities
Branch: master
https://github.com/mongodb/mongo/commit/ef5ab5ec47cbd9f261c097f83529f7e70d0c85d3

Comment by Eric Milkie [ 15/Nov/16 ]

In the linked ticket, an end user makes an argument that they are actionable.

Comment by Andy Schwerin [ 15/Nov/16 ]

Are msgassert or verify log messages actionable by the end user? I bet most of them aren't, which to me means they belong at the same severity as log().

Generated at Thu Feb 08 04:13:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.