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

Choose commit timestamp for transaction as max(prepare timestamps)

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.10
    • Component/s: Replication, Sharding
    • Labels:
      None

      Description

      Currently the cross-shard transaction coordinator chooses its commit timestamp as the maximum of the prepare timestamps plus one. Instead, it should choose the commit timestamp as the maximum of the prepare timestamps.

        Attachments

          Issue Links

          depends on

          Task - A task that needs to be done. SERVER-39035 Specify durable_timestamp when committing prepared transaction

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

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: