[SERVER-58165] Make RamLog limits configurable Created: 30/Jun/21  Updated: 03/Nov/23  Resolved: 25/Oct/22

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-58166 Resumable index build rollback tests ... Closed
is related to SERVER-82625 create_indexes_waits_for_already_in_p... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

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.



 Comments   
Comment by Connie Chen [ 25/Oct/22 ]

Decided to close as we do not want to rely on log lines for testing, but if someone wants it please re-open to be triaged (send to needs scheduling)

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