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

CommandNotFound: no such command: 'shardVersion'

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 4.4.26, 7.0.4
    • Affects Version/s: 4.4.11, 5.0.4, 6.0.0, 6.2.0-rc4
    • Component/s: None
    • Environment:
      os: centos 7 x86_64
      mongo version: 4.4.14
    • Sharding NYC
    • Fully Compatible
    • ALL
    • v7.0, v6.3, v6.0, v5.0, v4.4
    • Service Arch 2023-02-20, Service Arch 2023-03-06, Sharding NYC 2023-04-03, Sharding NYC 2023-04-17, Sharding NYC 2023-05-01, Sharding NYC 2023-05-15, Sharding NYC 2023-05-29, Sharding NYC 2023-06-12, Sharding NYC 2023-06-26, Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07, Sharding NYC 2023-08-21

      Early this AM I deploy the mongod data servers in our sharded (3 shards, 3 nodes each, no arbiter) cluster. Since deployed our monitoring system has been detecting an uptick in user assertions. I have been searching for a cause, and after setting the loglevel to 1 and grabbing a snippet from the logs, it appears that this is the error:

      {"t":{"$date":"2023-01-04T17:08:21.381+08:00"},"s":"D1", "c":"-",        "id":23074,   "ctx":"conn141332","msg":"User assertion","attr":{"error":"CommandNotFound: no such command: 'shardVersion'","file":"src/mongo/db/service_entry_point_common.cpp","line":1361}}
      {"t":{"$date":"2023-01-04T17:08:21.381+08:00"},"s":"D1", "c":"COMMAND",  "id":21966,   "ctx":"conn141332","msg":"Assertion while executing command","attr":{"command":"shardVersion","db":"orderdb","error":"CommandNotFound: no such command: 'shardVersion'"}}
      {"t":{"$date":"2023-01-04T17:08:21.381+08:00"},"s":"I",  "c":"COMMAND",  "id":51803,   "ctx":"conn141332","msg":"Slow query","attr":{"type":"command","ns":"orderdb.$cmd","command":"unrecognized","numYields":0,"ok":0,"errMsg":"no such command: 'shardVersion'","errName":"CommandNotFound","errCode":59,"locks":{},"protocol":"op_msg","durationMillis":0}}
      {"t":{"$date":"2023-01-04T17:08:21.381+08:00"},"s":"D1", "c":"QUERY",    "id":22790,   "ctx":"conn141332","msg":"Received interrupt request for unknown op","attr":{"opId":3652609564}} 

      This is happening on all 2 secondary shard servers, but not the primaries. The collections in these sharded dbs are still getting new documents, and replication appears to be working fine. I have not upgraded the mongos instances yet, those will be this weekend/next week to prevent impacts on production apps. Anyone know what might be causing this? Is this a bug for mongodb 4.4.x?






            jada.lilleboe@mongodb.com Jada Lilleboe (Inactive)
            335612970@qq.com dongyu si
            0 Vote for this issue
            7 Start watching this issue