[SERVER-14866] Replication from 2.4 primary to 2.6 secondaries failes on missing db in system.users Created: 12/Aug/14 Updated: 10/Dec/14 Resolved: 15/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robin Speekenbrink | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | have a 2.4(.10) primary with a 2.6(.3) secondary and update a user inside a database system.users : { |
||||||||||||
| Participants: | |||||||||||||
| Description |
|
I'm following the rolling upgrade procedure for upgrading my replication set to 2.6 (coming from 2.4) This works like it should except when encountering user credential updates...
Is there any way to have 2.6 secondaries without forcing the primary directly to 2.6 too? |
| Comments |
| Comment by Robin Speekenbrink [ 15/Aug/14 ] |
|
Spencer, Thanks for the update and the clearification. This indeed is not reflected by the documentation at all: its supposed to be a full on backwards compatible change (i.e. http://docs.mongodb.org/manual/release-notes/2.6-upgrade-authorization/#timing where it's advised to leave the incompatible state for a while) Anyway, this has forced us to upgrade the remaining mongod-instances to 2.6 .... To bad the rolling update process wasn't really that rolling Thanks again for the udpate! |
| Comment by Spencer Brody (Inactive) [ 13/Aug/14 ] |
|
Hi Robin, Unfortunately this is the expected behavior. Due to the new schema for user documents in 2.6, once you have begun upgrading to 2.6, all user data is immutable until every node is on 2.6 and you have run the authorization data schema upgrade. Your full replica set must either be all on 2.4 or 2.6 if you want to be able to modify user definitions. I have filed |