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

abortTransaction and commitTransaction commands should not acquire ticket irrespective of the prepared state.

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2, v4.0
    • Sprint:
      Repl 2019-07-29

      Description

      Currently, if a transaction is prepared, we don't acquire ticket due to SERVER-41980. We have ticketing mechanism to throttle readers and writers from overwhelming the storage resources. Also, when a ticket is acquired, it indicates that the operation/cmd is going to acquire more storage resources. But, both abortTransaction and commitTransaction cmd are not going to acquire any more storage resources (except writing to oplog) instead they are going to release the storage resources. So, to have a general solution, abortTransaction and commitTransaction commands should not acquire ticket.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: