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

Secondaries fassert when replicating createCollection op with missing size value

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.1.2
    • 3.1.4
    • Replication
    • Fully Compatible
    • ALL
    • Hide

      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();
      

      Show
      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();

    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
      

      Attachments

        Activity

          People

            matt.dannenberg Matt Dannenberg
            kamran.khan Kamran K.
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: