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

Unify the different ways the TransactionParticipant offers for aborting a transaction

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.1, 4.3.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2
    • Sprint:
      Repl 2019-07-01, Repl 2019-07-15, Repl 2019-07-29, Repl 2019-08-12, Repl 2019-08-26

      Description

      The TransactionParticipant currently has at least 6 different code paths, which can abort a transaction, with slightly different implementation details between them:

      My suspicion is that this was done because there didn't use to be a good concurrency control between checking the state of the TransactionParticipant from outside and making abort decisions. Given that currently we have the Client lock concurrency control mechanism in place, all these different abort paths can be unified into some common denominator that they all share and the rest of the checks that they do can be pulled out into the calling sites.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matthew.russotto Matthew Russotto
              Reporter:
              kaloian.manassiev Kaloian Manassiev
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: