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

ShardingTest doesn't show logs on stdout

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc0, 4.7.0
    • Affects Version/s: 4.3.2, 4.3.3
    • Component/s: Logging, Shell
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v4.4
    • Hide

      Open a mongo shell:
      mongo --nodb
      Instantiate a cluster:
      cl = ShardingTest({});

      Connect to the mongos through another shell and run this command:
      db.adminCommand({ setParameter: 1, logComponentVerbosity: { replication: { heartbeats: 0}}});

      In the mongos log output you should see an entry like this:
      2019-12-18T09:39:46.523+0000 I COMMAND [conn7] successfully set parameter logComponentVerbosity to ...
       

      Show
      Open a mongo shell: mongo --nodb Instantiate a cluster: cl = ShardingTest({}); Connect to the mongos through another shell and run this command: db.adminCommand({ setParameter: 1, logComponentVerbosity: { replication: { heartbeats: 0}}}); In the mongos log output you should see an entry like this: 2019-12-18T09:39:46.523+0000 I COMMAND [conn7] successfully set parameter logComponentVerbosity to ...  
    • Dev Tools 2020-02-10, Dev Tools 2020-02-24, Dev Tools 2020-03-09, Dev Tools 2020-03-23

      After the creation of a ShardingTest() on the mongo shell logs for all the spawned processes of the cluster are supposed to be redirected to the stdout of the console on which ShardingTest has been executed.
      Currently I'm only able to see logs of the components during the startup and shutdown phase of ShardingTest(), but not at runtime.

            Assignee:
            henrik.edin@mongodb.com Henrik Edin
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: