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

Document how to handle oplog format changes for upgrade/downgrade

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication

      A very common issue that projects often run into is oplog format changes and handling them across versions. Newer versions need to ensure they are compatible with older version oplog entries so that they do not crash. We should document how to address this problem and standardize the procedure so that engineers have something they can reference while working on their tickets

            Assignee:
            Unassigned Unassigned
            Reporter:
            xuerui.fa@mongodb.com Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: