[SERVER-15516] 2.6.x secondaries cannot apply update performed by 2.4.x primary, fassert Created: 02/Oct/14  Updated: 10/Dec/14  Resolved: 08/Dec/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.6.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Asya Kamsky Assignee: Eric Milkie
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-6852 Disallow empty path components in doc... Backlog
Operating System: ALL
Steps To Reproduce:

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

Participants:

 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


Generated at Thu Feb 08 03:38:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.