Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-30387

maxLogSizeKB parameter should only be positive

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.4.0
    • Component/s: Internal Code, Logging
    • Minor Change
    • Sharding 2018-03-12, Sharding 2019-02-25, Sharding 2019-03-11, Sharding 2019-03-25, Dev Tools 2020-03-09

      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).

            Assignee:
            henrik.edin@mongodb.com Henrik Edin
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: