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

Remove code for parsing and handling config server connection string during sharding state recovery

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.7.1
    • None
    • Sharding
    • Fully Compatible
    • Sharding 2017-01-02, Sharding 2017-12-18

    Description

      In 3.4 we stop writing the shardId and config server connection string to the minOpTimeRecovery document, as that information is redundant of information present in the shardIdentity document. We still handle reading that information, however, to handle backwards compatibility during upgrade from 3.2 to 3.4. During the 3.6 dev cycle this can be removed.

      Attachments

        Activity

          People

            kaitlin.mahar@mongodb.com Kaitlin Mahar
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: