[SERVER-61484] Allow ExceededMemoryLimit to be a benign log warning instead of an invariant in the JournalFlusher Created: 15/Nov/21  Updated: 29/Oct/23  Resolved: 06/Dec/21

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-61300 Investigate memory usage of exact-top... Closed
Related
related to SERVER-79810 make JournalFlusher::waitForJournalFl... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-12-13
Participants:
Linked BF Score: 35

 Description   

The jstestfuzzer provoked a WT cache full error on the in-memory engine. This should only be an issue for the in-memory engine – the durable engine should be in a panic evicting mode before this could happen. The server invariants on the error here in the JournalFlusher

We should log the warning and continue – the journal flusher runs periodically and would repeatedly log the error message, and cmds waiting for j:true would return the error message.



 Comments   
Comment by Githook User [ 06/Dec/21 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}

Message: SERVER-61484 JournalFlusher should log a warning on ExceededMemoryLimit errors rather than crash
Branch: master
https://github.com/mongodb/mongo/commit/ce6aa8504efc89566558eba86bb753076b36472c

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