[DOCS-13485] Investigate changes in SERVER-30387: maxLogSizeKB parameter should only be positive Created: 02/Mar/20 Updated: 30/Oct/23 Due: 27/Mar/20 Resolved: 08/Jun/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Andrew Feierabend (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 3 years, 35 weeks, 2 days ago | ||||||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||||||
| Description |
DescriptionDownstream Change Summary The semantics of the maxLogSizeKB server parameter have changed slightly in the change to structured logging. It no longer applies to the textual (json) log line (only the attrs), truncation is done in a different way, and setting it to 0 disables all truncation. Description of Linked TicketIt's currently possible to set the maxLogSizeKB parameter to 0 or a negative value, neither of which make sense. The parameter variable itself is a signed int, but gets assigned to a size_t (which is unsigned). But it's not possible to use an unsigned type (see Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 08/Jun/20 ] |
|
Author: {'name': 'Andrew Feierabend', 'email': 'andrew.feierabend@mongodb.com', 'username': 'andf-mongodb'}Message: DOCSP-7684, |