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

mongos CollectionStats command is too verbose

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Sharding
    • ALL

      Running the collstats command on mongos with today's server results in up to 6 messages to the mongos system log:

      [ShardedClusterFixture:job0:mongos0] 2018-11-13T20:18:25.359+0000 I COMMAND  [conn67] mongos collstats doesn't know about: sleepCount
[ShardedClusterFixture:job0:mongos0] 2018-11-13T20:18:25.359+0000 I COMMAND  [conn67] mongos collstats doesn't know about: sleepMS
[ShardedClusterFixture:job0:mongos0] 2018-11-13T20:18:25.359+0000 I COMMAND  [conn67] mongos collstats doesn't know about: $gleStats
[ShardedClusterFixture:job0:mongos0] 2018-11-13T20:18:25.359+0000 I COMMAND  [conn67] mongos collstats doesn't know about: lastCommittedOpTime
[ShardedClusterFixture:job0:mongos0] 2018-11-13T20:18:25.359+0000 I COMMAND  [conn67] mongos collstats doesn't know about: $clusterTime
[ShardedClusterFixture:job0:mongos0] 2018-11-13T20:18:25.359+0000 I COMMAND  [conn67] mongos collstats doesn't know about: operationTime

      That seems too verbose for a simple command such as this one.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: