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

Inconsistent appName in Shard

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6, v3.4
    • Sprint:
      Platforms 2018-05-07

      Description

      We have around 100 applications that send appName to a MongoDB Shard and 100 that do not send appName and sometimes MongoDB shows an appName that is not the correct one.
      Case 1: When we run a query in the shell sometimes takes the appName from one of the applications it is running. We tested in shell version 3.2.10 by connecting in Mongos 3.4.13 and this happened in the second query executed (the first time was without appName, the second got appName from a random application).

      mongos> db.investigation_users.find({teste: 1})
      mongos> db.currentOp()
       
      "appName" : "fetcherperf-rt1 - Fetcher - 3.0.9"
      "query" : {
              "find" : "investigation_users",
              "filter" : {
                      "teste" : 1
              },
              "shardVersion" : [
                      Timestamp(430, 0),
                      ObjectId("5a0a72f8b1199455c0f4b3c2")
              ]
      }
      

      Case 2: appName that are no longer used appear in operations of other applications. We had configured an application with the name "devops", but then we changed it to "devops - 1.3.2". The second appName started to appear in the operations, but the "devops" also appeared even with no application sending it anymore..

      The attached file is an example of a shell execution and currentOp command showed an appName of an application.

        Attachments

        1. appName_invalid.log
          8 kB
        2. error.json
          79 kB
        3. screenshot-1.png
          screenshot-1.png
          78 kB

          Activity

            People

            • Votes:
              2 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: