Execution Architecture Guide: Storage Transactions

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Execution Team 2020-08-10, Execution Team 2020-08-24
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Rough starting outline:

      Storage Transactions
              (clarify transaction refers to storage engine transactions, not repl or sharding, throughout this document)
              (include a discussion on how RecoveryUnit implements isolation and transactional behaviors, including ‘read source’ and how those implement read concern levels)
              (Maybe include a discussion of how MongoDB read concerns translate into particular read sources and data views.)
          WiredTiger Snapshot
          MongoDB Point-in-Time Reads
      

      Definitely feel free to alter the layout and file additional tickets split the work into more manageable units. Please add topics if you can think of any. This outline is meant only to be a starting point.

      A couple helpful links for markdown basics:
      https://www.markdowntutorial.com/
      https://gist.github.com/asabaylus/3071099
      https://markdownlivepreview.com/

            Assignee:
            Eric Milkie
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: