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.
- includes Epic(s)
-
SERVER-100407 Increase RamLog size during testing
-
- Closed
-
- is depended on by
-
SERVER-107669 Create startup parameters to configure RamLog constraints
-
- Open
-
-
SERVER-90400 Robustify tests that check for messages in the mongod log
-
- Backlog
-
- is related to
-
SERVER-58166 Resumable index build rollback tests can run out of RamLog space
-
- Closed
-
-
SERVER-82625 create_indexes_waits_for_already_in_progress.js random fail due to using checkLog
-
- Closed
-
-
SERVER-100407 Increase RamLog size during testing
-
- Closed
-
-
SERVER-90346 Test resumable index builds without checking log lines
-
- Backlog
-
- related to
-
SERVER-107669 Create startup parameters to configure RamLog constraints
-
- Open
-