Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-340

Make minimum value of maxStalenessSeconds 90 seconds

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Component/s: None
    • None

      This supersedes DRIVERS-335. The only part of that ticket which is still relevant is:

      • Rename maxStalenessMS to maxStalenessSeconds

      These parts of DRIVERS-335 are reverted:

      • Parse idleWritePeriodMillis from isMaster, in case a future server version ever includes it (reverted, the idle write period is a 10 second constant you define in your driver code)
      • The maxStalenessSeconds can be a float (reverted, it's an integer)
      • The smallest value is now heartbeatFrequencyMS + idleWritePeriodMS (superseded, it must now also be at least 90 seconds)

      DRIVERS-336 is not superseded, it's still valid: the default value for maxStalenessSeconds is -1, meaning "no max staleness". maxStalenessSeconds=0 is prohibited.

      Now, to complete this ticket:

      • The smallest value for maxStalenessSeconds is now 90 seconds or heartbeatFrequencyMS + idleWritePeriodMS (10 seconds), whichever is greater.
      • Resync Max Staleness JSON tests - they are tagged max-staleness-tests-2016-11-22
      • Review Max Staleness prose tests and update your tests

            Assignee:
            rathi.gnanasekaran Rathi Gnanasekaran
            Reporter:
            rathi.gnanasekaran Rathi Gnanasekaran
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: