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

2.6 initial sync should fail if syncing from 3.0+WT

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 2.6.10
    • Fix Version/s: None
    • Component/s: Replication, WiredTiger
    • Labels:
      None
    • Environment:
      2.6.10 initial sync using 3.0.4 (WiredTiger) as the sync source

      Description

      Currently, it's possible to perform initial sync of a 2.6 node using 3.0+WT as the source. The process finishes successfully without any errors in the logs. However, no indexes are cloned:

      2015-06-29T17:36:59.844-0400 [rsSync] oplog sync 1 of 3
      2015-06-29T17:36:59.844-0400 [rsSync] oplog sync 2 of 3
      2015-06-29T17:36:59.845-0400 [rsSync] replSet initial sync building indexes
      2015-06-29T17:36:59.845-0400 [rsSync] replSet initial sync cloning indexes for : test
      2015-06-29T17:36:59.845-0400 [rsSync] oplog sync 3 of 3
      2015-06-29T17:36:59.845-0400 [rsSync] replSet initial sync finishing up
      2015-06-29T17:36:59.853-0400 [rsSync] replSet set minValid=5591b938:1
      2015-06-29T17:36:59.858-0400 [rsSync] replSet RECOVERING
      2015-06-29T17:36:59.858-0400 [rsSync] replSet initial sync done
      2015-06-29T17:37:00.859-0400 [rsSync] replSet SECONDARY
      

      While the documentation is very clear that in order to downgrade 3.0+WT you need to switch to 3.0+MMAP first, it's counter-intuitive that the initial sync process successfully completes in the above case while a critical piece of it has obviously failed. I would expect the initial sync process to error out.

      -Alex

        Attachments

          Activity

            People

            Assignee:
            backlog-server-repl Backlog - Replication Team
            Reporter:
            alex.komyagin Alexander Komyagin
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: