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

Enforce maxStalenessSeconds >= 90

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.2, 3.5.1
    • Affects Version/s: 3.4.0-rc4
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • v3.4
    • Sharding 2016-12-12, Sharding 2017-01-02

      Changes to max staleness spec:

      The $readPreference option "maxStalenessSeconds" is no longer allowed to be double, it's once again only int32 or int64. (This change can be put off, need not block 3.4.)

      The minimum is now 90 seconds. (3.4 blocker.)

      See the "mongos tests" section here:

      https://github.com/mongodb/specifications/blob/master/source/max-staleness/max-staleness-tests.rst#mongos

      cc schwerin misha.tyulenev

            Assignee:
            misha.tyulenev@mongodb.com Misha Tyulenev
            Reporter:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: