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

Replication from 2.4 primary to 2.6 secondaries failes on missing db in system.users

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • ALL
    • Hide

      have a 2.4(.10) primary with a 2.6(.3) secondary and update a user inside a database system.users :

      {
      "_id": ObjectId("52cd1973dd44e5b4fe9c84b7"),
      "user": "test",
      "pwd": "testpassword",
      "roles": [
      "read",
      "readWrite"
      ]
      }

      Show
      have a 2.4(.10) primary with a 2.6(.3) secondary and update a user inside a database system.users : { "_id": ObjectId("52cd1973dd44e5b4fe9c84b7"), "user": "test", "pwd": "testpassword", "roles": [ "read", "readWrite" ] }

      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?

            Assignee:
            Unassigned Unassigned
            Reporter:
            gekkie Robin Speekenbrink
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: