Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Works as Designed
-
None
-
None
-
None
-
ALL
-
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...
This does not work in a backwards compatible way (due to the new system.users layout...)
2014-08-12T11:54:58.653+0200 [repl writer worker 3] ERROR: writer worker caught exception: :: caused by :: 2 User document needs 'db' field to be a non-empty string on: { ts: Timestamp 1407584109000|1, h: 1483884049638091315, v: 2, op: "u", ns: "communibase_noloc_test.system.users", o2: { _id: ObjectId('52cd1973dd44e5b4fe9c84b7') }, o: { _id: ObjectId('52cd1973dd44e5b4fe9c84b7'), user: "xWdMA8qmytKAc7m", pwd: "a456218d1d878d9d53963503af28b328", roles: [] } }
|
2014-08-12T11:54:58.654+0200 [repl writer worker 3] Fatal Assertion 16360
|
2014-08-12T11:54:58.654+0200 [repl writer worker 3]
|
|
***aborting after fassert() failure
|
Is there any way to have 2.6 secondaries without forcing the primary directly to 2.6 too?
Attachments
Issue Links
- related to
-
DOCS-3899 Clarify that all user data is immutable once a single node in a replica set is on 2.6, until they run the user upgrade
-
- Closed
-
-
SERVER-14887 Allow user document changes made on a 2.4 primary to replicate to a 2.6 secondary
-
- Closed
-