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

Renaming a collection with newly added background indexes may fail to replicate

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • 2.6.4, 2.7.4
    • 2.7.5
    • Index Maintenance, Replication
    • None
    • ALL
    • Hide 

      use db1
      		 
      db.content.ensureIndex({a:1}, {background:true})
      		 
      db.content.insert({})
      		 
      db.adminCommand({renameCollection: 'db1.content', to: 'db2.content', dropTarget: true})

      Show
      use db1 db.content.ensureIndex({a:1}, {background:true}) db.content.insert({}) db.adminCommand({renameCollection: 'db1.content', to: 'db2.content', dropTarget: true})

    Description

      After renaming a collection which contains background indexes, the collection will be successfully renamed on the primary, correctly recorded in the oplog, but does not replicate, ie. the collection will not have been renamed on the secondaries. This is due to the following error on the secondaries:

      2014-09-25T15:56:39.080+1000 [repl writer worker 1] build index on: db2.content properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "db2.content" }
      		 
      2014-09-25T15:56:39.080+1000 [repl writer worker 1]      building index using bulk method
      		 
      2014-09-25T15:56:39.080+1000 [repl writer worker 1] build index done.  scanned 1 total records. 0 secs
      		 
      2014-09-25T15:56:39.080+1000 [repl writer worker 1] build index on: db2.content properties: { v: 1, key: { a: 1.0 }, name: "a_1", ns: "db2.content", background: true }
      		 
      2014-09-25T15:56:39.083+1000 [repl writer worker 1] index build failed. spec: { v: 1, key: { a: 1.0 }, name: "a_1", ns: "db2.content", background: true } error: 13130 can't start bg index b/c in recursive lock (db.eval?)
      		 
      2014-09-25T15:56:39.083+1000 [repl writer worker 1] restarting 0 index build(s)
      		 
      2014-09-25T15:56:39.083+1000 [repl writer worker 1] warning: repl Failed command { renameCollection: "db1.content", to: "db2.content", dropTarget: true } on admin with status UnknownError Location13130 can't start bg index b/c in recursive lock (db.eval?) during oplog application
      		 
      2014-09-25T15:56:48.965+1000 [repl writer worker 1] warning: repl Failed command { renameCollection: "db2.content", to: "db1.content", dropTarget: true } on admin with status UnknownError source namespace does not exist during oplog application

      The problem does not occur in 2.7.5, so it must have been fixed between 2.7.4 and 2.7.5. It's still present in 2.6.4.

      Attachments

        Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-4941 collection rename may not replicate / clone properly during initial sync

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-16274 secondary fasserts trying to replicate an index

          • Major - P3 - Major loss of function.
          • Closed
          tested by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-16943 Add test for compatibility of replset background index and renameCollection

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              milkie@mongodb.com Eric Milkie
              kevin.pulo@mongodb.com Kevin Pulo
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: