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

createOplogFetchingPipelineForResharding() should filter out applyOps entries for aborted transactions

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • Sharding 2021-01-25
    • 1

    Description

      The ReshardingAggTest::VerifyPipelineXXXXAbort() tests are currently failing because the applyOps entries are left behind even though there is an abortTransaction entry at then end of the chain. 

      There is code in the createOplogFetchingPipelineForResharding() function that appears to filter these entries out but it does not seem to be working according to the tests.

      Attachments

        Issue Links

          Activity

            People

              max.hirschhorn@mongodb.com Max Hirschhorn
              alex.taskov@mongodb.com Alexander Taskov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: