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

Summarize the occurrence where we read or write config.transactions collection

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Repl 2024-12-09, Repl 2024-12-23
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      • Summarize the findings in a google doc.
      • This should include primary, secondary and sharded cluster migration cases.
      • For each occurrence, what we are interested is:
        • The purpose of accessing the `config.transactions` collection.
        • How we access the `config.transactions` collection (e.g. read or write, point read or scan)

      This could help us ramp up on the background, guide the design for this project as well as future projects.

            Assignee:
            m.maher@mongodb.com Moustafa Maher
            Reporter:
            wenbin.zhu@mongodb.com Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: