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

Remove informational message on overflow file size quota

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.13
    • Affects Version/s: 4.0.12
    • Component/s: None
    • Labels:
    • Fully Compatible
    • Storage Engines 2019-09-09, Storage Engines 2019-09-23
    • 1

      The backport of SERVER-39004 to v4.0 introduced a msg to stdout when starting mongod that logs the value of wiredTigerMaxCacheOverflowFileSizeGB setting even when set to its default value of 0.

      alexc@kitty:~/work/mongo$ ./mongod --logpath=data/mongod.log --dbpath=data/ --fork
      2019-08-14T00:33:16.654+0000 I STORAGE  [main] Max cache overflow file size custom option: 0
      about to fork child process, waiting until server is ready for connections.
      forked process: 27798
      child process started successfully, parent exiting

      A normal invocation of mongod shouldn't be causing the setting to be written to stdout like this. It'd be acceptable to only print it when explicitly set (like the wiredTigerEngineConfig option) or to just not print it at all.

            alex.cameron@mongodb.com Alex Cameron (Inactive)
            alex.cameron@mongodb.com Alex Cameron (Inactive)
            1 Vote for this issue
            9 Start watching this issue