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

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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 2.6.4
    • 2.6.5, 2.7.7
    • Replication, Security
    • None
    • Minor Change
    • ALL

    Description

      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().

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-14866 Replication from 2.4 primary to 2.6 secondaries failes on missing db in system.users

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-15360 User document changes made on a 2.4 primary and replicated to a 2.6 secondary don't make the 2.6 secondary invalidate its user cache

          • Major - P3 - Major loss of function.
          • Closed
          tested by

          Task - A task that needs to be done. SERVER-15515 New test for mixed version replSet, 2.4 primary, user updates

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              spencer@mongodb.com Spencer Brody (Inactive)
              spencer@mongodb.com Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: