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

Initial syncing node maintains tmp collection from map reduce when primary has renamed it

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 3.3.9
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 17 (07/15/16), Repl 18 (08/05/16), Repl 2016-08-29
    • 0

    Description

      When running the small_oplog_rs_initsync passthrough we get an error where a temporary collection created in a mapreduce is not renamed on teh secondary even though it is on the primary.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-25332 Initial sync bootstrap needs to handle collection metadata changes idempotently

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

          Task - A task that needs to be done. SERVER-26117 renameCollection 'c' op should restart initial sync upon application

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

          Activity

            People

              siyuan.zhou@mongodb.com Siyuan Zhou
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: