[SERVER-18792] Secondaries fassert when replicating createCollection op with missing size value Created: 02/Jun/15  Updated: 19/Sep/15  Resolved: 04/Jun/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.1.2
Fix Version/s: 3.1.4

Type: Bug Priority: Major - P3
Reporter: Kamran K. Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: 32qa, FT
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

var rst = new ReplSetTest({nodes: 2});
rst.startSet();
rst.initiate();
rst.awaitSecondaryNodes();
 
var testDB = rst.getPrimary().getDB('test');
testDB.dropDatabase();
 
testDB.createCollection('foo', {capped: true, size: 0});
rst.awaitSecondaryNodes();

Participants:

 Description   

This bug affects versions 3.1.2+. It does not affect 3.0.x.

It was introduced in this commit range, so the changes from SERVER-15860 and/or SERVER-15207 are the likely culprits.

m31001|  E REPL     [repl writer worker 15] Failed command { create: "foo", capped: true } on test with status Location14832 specify size:<n> when capped is true during oplog application
m31001|  I -        [repl writer worker 15] Fatal Assertion 16359
m31001|  I -        [repl writer worker 15] 
m31001| 
m31001| ***aborting after fassert() failure



 Comments   
Comment by Githook User [ 04/Jun/15 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-18792 when logging createCollection to the oplog always include size if capped:true
Branch: master
https://github.com/mongodb/mongo/commit/dfd0d0cfca72c443072d18fd141957d1cf30ef1f

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