Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13485

Investigate changes in SERVER-30387: maxLogSizeKB parameter should only be positive

XMLWordPrintableJSON

      Description

      Downstream 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 Ticket

      It'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 SERVER-27520), so either the allowed values should be restricted to only > 0, or values <= 0 reinterpreted (eg. to mean "default value" of 10 KB).

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            Assignee:
            andrew.feierabend@mongodb.com Andrew Feierabend (Inactive)
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              3 years, 45 weeks, 3 days ago