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

Migration can miss writes from prepared transactions

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • 4.2.0, 4.4.0, 5.0.0, 6.0.0, 6.1.0-rc3
    • 4.4.19, 5.0.15, 6.3.0-rc0, 6.0.5
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v6.2, v6.0, v5.0, v4.4
    • Hide

      Uncomment this line in test

      Show
      Uncomment this line in test
    • Sharding NYC 2022-11-28, Sharding 2022-12-12, Sharding NYC 2022-12-26, Sharding NYC 2023-01-09, Sharding NYC 2023-01-23, Sharding NYC 2023-02-06
    • 113

    Description

      Migration relies on LogTransactionOperationsForShardingHandler to capture writes that gets committed. However, the issue is that the commit handler only gets registered to the recovery unit during prepare. This means that if another node becomes the primary, no callbacks from LogTransactionOperationsForShardingHandler will get called when the transaction gets committed.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-68361 LogTransactionOperationsForShardingHandler::commit misses transferring documents from prepared and non-prepared transactions changing a document's shard key value

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. SERVER-38284 Remove donor collection X-lock acquisition for starting the clone phase

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              randolph@mongodb.com Randolph Tan
              randolph@mongodb.com Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: