-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Networking & Observability
-
N&O Prioritized List
-
0
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently, RamLog hardcodes the maximum number of lines and maximum number of bytes it can store. However, it would be useful to increase these limits for certain tests which rely on getLog and can generate a large number of log lines in certain conditions, causing log lines of interest to fall off the end of the buffer and be missed. We should look into in making these limits configurable via startup parameters.
- is depended on by
-
SERVER-90400 Robustify tests that check for messages in the mongod log
-
- Blocked
-
- is related to
-
SERVER-58166 Resumable index build rollback tests can run out of RamLog space
-
- Closed
-
-
-
- Closed
-
-
-
- Backlog
-
-
SERVER-90346 Test resumable index builds without checking log lines
-
- Backlog
-