[SERVER-38233] Logging should not silently ignore errors Created: 23/Nov/18 Updated: 29/Oct/23 Resolved: 24/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Henrik Edin |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.4
|
||||
| Sprint: | Execution Team 2020-04-06, Dev Tools 2020-03-09 | ||||
| Participants: | |||||
| Description |
|
Currently, any failure to append a log message is silently ignored (even though the appenders report failures). (Note that LogDomain's _abortOnFailure is initialised as false and only set to true for the audit log.) This isn't great, because it means that any given logfile might not actually be a complete record of the server's behaviour, which is an assumption that logfile analysis very frequently relies on. Also, in the event of a permanent logging failure (eg. the logfile filesystem goes read-only), the server will continue to run (potentially for a long period of time) with no indication of any problem. Possible solutions might include:
|
| Comments |
| Comment by Githook User [ 26/Mar/20 ] |
|
Author: {'name': 'Henrik Edin', 'username': 'henrikedin', 'email': 'henrik.edin@mongodb.com'}Message: (cherry picked from commit e6e75a8bb7c95cca2a5f7ed028d497efbfe51078) |
| Comment by Githook User [ 24/Mar/20 ] |
|
Author: {'email': 'henrik.edin@mongodb.com', 'name': 'Henrik Edin', 'username': 'henrikedin'}Message: |
| Comment by Matt Lord (Inactive) [ 04/Dec/18 ] |
|
I think that a new parameter called ~ abortOnLogFailure, defaulting to off, would make sense. |