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

Investigate non-deterministic RPU count in retryable findAndModify

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Service Arch

    Description

      The investigation in a recent support ticket identified non-determinism in billing metrics for a retryable findAndModify command. A retryable findAndModify operation will store a copy of the preimage in order to support transparent retries. The operation will perform an upsert in config.image_collection, keyed by the lsid. The current working theory is that something about the conditions in the test is occasionally triggering upsert, which requires an additional read which we are not filtering out of billing metrics. 

      In this ticket, we should try develop a local reproducer so that we can improve our confidence in SERVER-73666 as a solution. 

       

       

       

       

      Attachments

        Activity

          People

            backlog-server-servicearch Backlog - Service Architecture
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: