Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14433

Investigate changes in SERVER-55578: Disallow atClusterTime reads on the config.transactions collection

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0-rc0
    • Component/s: manual, Server
    • Labels:
      None

      Description

      Description

      Downstream Change Summary

      Non-transaction reads on config.transactions collection with readConcern snapshot are disallowed.
      Non-transaction reads on config.transactions collection with readConcern majority and afterClusterTime (e.g. in a causal consistent session) are disallowed.

      Description of Linked Ticket

      The changes from SERVER-55305 will address how a retryable write statement may execute multiple times without making atClusterTime reads on the config.transactions collection correct for all readTimestamps. To prevent accidental misuse of atClusterTime reads, they should be rejected on the config.transactions collection.

      Note however that resharding depends on performing an atClusterTime read on the config.transactions collection (see SERVER-55214) and will need an undocumented option (or some internal privilege way) of continuing to use atClusterTime reads on the config.transactions collection.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ian.fogelman Ian Fogelman
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Ian Fogelman Ian Fogelman
              Docs Reviewer:
              Dave Cuthbert Dave Cuthbert
              External Reviewer:
              Lingzhi Deng
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                2 weeks ago
                Date of 1st Reply: