-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.6.4
-
Component/s: Replication, Security
-
None
-
Minor Change
-
ALL
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().
- is related to
-
SERVER-14866 Replication from 2.4 primary to 2.6 secondaries failes on missing db in system.users
- Closed
-
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
- Closed
- tested by
-
SERVER-15515 New test for mixed version replSet, 2.4 primary, user updates
- Closed