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

2.6.x secondaries cannot apply update performed by 2.4.x primary, fassert

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 2.6.4
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      Update on the primary of mixed set as follows:
      db.foo.update({},{$inc:{"":1}})

      Show
      Update on the primary of mixed set as follows: db.foo.update({},{$inc:{"":1}})

      Description

      If 2.4.x primary accepts an update which sets a field named "" (see related SERVER-6852) when 2.6.x tries to replicate it, it gets an fassert since 2.6.x primary would not allow such an update.

      [repl writer worker 1] ERROR: writer worker caught exception:  :: caused by :: 56 An empty update path is not valid. on: { ts: Timestamp 1412277396000|1, h: 7945760602220701657, v: 2, op: "u", ns: "test.visitors", o2: { _id: 1.0 }, o: { $set: { : 1.0 } } }
      2014-10-02T15:21:52.352-0400 [repl writer worker 1] Fatal Assertion 16360
      2014-10-02T15:21:52.352-0400 [repl writer worker 1]
       
      ***aborting after fassert() failure

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              milkie Eric Milkie
              Reporter:
              asya Asya Kamsky
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: