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

Transaction failed after version upgrade

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sharding EMEA
    • ALL

      We have a sharded cluster with one shard. After upgrading from version 4.4 to 5, an error was received at the application level:

      Command failed with error 13388 (StaleConfig): 'Transaction d5d7e6d6-3a64-48a1-bb4b-89742bc77ff8:5 was aborted on statement 7 due to: an error from cluster data placement change :: caused by :: findAndModify :: caused by :: sharding status of collection list-ks.orgnumbers is not currently available for description and needs to be recovered from the config server' on server sel-mongo01.imp.dks.lanit.ru:27017. The full response is {"ok": 0.0, "errmsg": "Transaction d5d7e6d6-3a64-48a1-bb4b-89742bc77ff8:5 was aborted on statement 7 due to: an error from cluster data placement change :: caused by :: findAndModify :: caused by :: sharding status of collection list-ks.orgnumbers is not currently available for description and needs to be recovered from the config server", "code": 13388, "codeName": "StaleConfig", "ns": "list-ks.orgnumbers", "vReceived": {"$timestamp": {"t": 0, "i": 0}}, "vReceivedEpoch": {"$oid": "000000000000000000000000"}, "shardId": "rs0", "$clusterTime": {"clusterTime": {"$timestamp": {"t": 1676462531, "i": 2}}, "signature": {"hash": {"$binary": {"base64": "TdIK36bailsmfPg8EbZ8Jh6TEM8=", "subType": "00"}}, "keyId": 7155588327440121859}}, "operationTime": {"$timestamp": {"t": 1676462531, "i": 2}}, "errorLabels": ["TransientTransactionError"]} 
      

      Only this was found in the logs:

      {"t":{"$date":"2023-02-15T12:02:11.217+00:00"},"s":"I",  "c":"SH_REFR",  "id":4619902, "ctx":"CatalogCache-3713","msg":"Collection has found to be unsharded after refresh","attr":{"namespace":"list-ks.orgnumbers","durationMillis":2}}
      {"t":{"$date":"2023-02-15T12:02:11.217+00:00"},"s":"I",  "c":"SHARDING", "id":21917,   "ctx":"RecoverRefreshThread","msg":"Marking collection as unsharded","attr":{"namespace":"list-ks.orgnumbers"}}
      {"t":{"$date":"2023-02-15T12:02:11.217+00:00"},"s":"I",  "c":"COMMAND",  "id":518070,  "ctx":"ShardServerCatalogCacheLoader::runCollAndChunksTasks","msg":"CMD: drop","attr":{"namespace":"config.cache.chunks.list-ks.orgnumbers"}}
      

      Can a version update be the cause of the error? If not an update, what could be the cause?

            Assignee:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Reporter:
            asik_asek@list.ru Asel Magzhanova
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: