Stop writing config server connection string and shard name to minOpTime recovery document

XMLWordPrintableJSON

    • Minor Change
    • v4.2
    • Sharding 2019-07-01
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We stopped using these fields in 3.6, but we still parse the minOpTime recovery document expecting to find them, returning a bad status if we can't. In 4.0, we stopped parsing these fields, but continued to write them, so when downgrading, a 3.6 node won't crash during sharding state recovery. After 4.0 ships, we can stop writing these fields.

              Assignee:
              Jason Zhang (Inactive)
              Reporter:
              Jack Mulrow
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: