Allow user document changes made on a 2.4 primary to replicate to a 2.6 secondary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.6.5, 2.7.7
    • Affects Version/s: 2.6.4
    • Component/s: Replication, Security
    • None
    • Minor Change
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Once you have upgraded to 2.6, user data is immutable until you run the user data upgrade. This is necessary and by design. However, it should be possible to allow user updates made in a mixed-mode cluster on a 2.4 primary to still replicate to a 2.6 secondary without crashing the 2.6. At the very least we should detect this and go into RECOVERING with a useful error message, rather than simply fasserting().

            Assignee:
            Spencer Brody (Inactive)
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: