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

"mongos collstats doesn't know about" clusterTime fields warning in 3.6

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Logging
    • Cluster Scalability
    • Sharding 2018-09-24

      In our logs we regularly find the following lines with "W" severity coming from out 3.6 cluster mongos routers:

       

      Unable to find source-code formatter for language: node. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
      2018-08-22T09:01:59.913+0900 W COMMAND  [conn13334] mongos collstats doesn't know about: operationTime
      2018-08-22T09:01:59.913+0900 W COMMAND  [conn13334] mongos collstats doesn't know about: gleStats
      2018-08-22T09:01:59.913+0900 W COMMAND  [conn13334] mongos collstats doesn't know about: clusterTime
      2018-08-22T09:01:59.913+0900 W COMMAND  [conn13334] mongos collstats doesn't know about: configServerState
      

      It seems this warning was added in MongoDB v1.8 as reasonable warning against fields that shouldn't be included when executing the command on a mongos router (SERVER-2752), but it wasn't updated to accept the fields for the 'logical time' clock (SERVER-27745) (since renamed "clusterTime") that were added in 3.6.

      I see in the v4.0 code it doesn't have this logic any more, but we won't be moving to 4.0 anytime soon. So just for the next minor version in the v3.6 branch could that block of code in the mongo/s/commands/commands_public.cpp file's CollectionStats::run() function be fixed to also ignore the "operationTime", "gleStats", "clusterTime", "configServerState" fields?

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            akira.kurogane@gmail.com 章 黒鉄
            Votes:
            7 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated: