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

When featureCompatibilityVersion is 3.2, a 3.4 node can't initial sync decimal data

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.3.14
    • Querying
    • None
    • Fully Compatible
    • ALL
    • Query 2016-09-19, Query 2016-10-10
    • 0

    Description

      If the primary has featureCompatibilityVersion 3.4, and during initial sync, we copy over decimal data before copying admin.system.version, then we reject the decimal data, and the initial sync fails.

      We would also like to successfully initial sync from a primary with featureCompatibilityVersion 3.2 that has decimal data, since a user can get into this state by inserting decimal data and then setting featureCompatibilityVersion to 3.2.

      Attachments

        Issue Links

          Activity

            People

              david.storch@mongodb.com David Storch
              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: