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

Server support for "maxStalenessMS" read preference option

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.12
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 18 (08/05/16), Sharding 2016-08-29, Sharding 2016-09-19

      Description

      This would be meta information returned with the query results

        Attachments

          Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-8723 3.4: add maxStalenessSeconds to read pref settings

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. DOCS-9544 Docs for SERVER-4936: Server support for "maxStalenessMS" read preference option

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          New Feature - A new feature of the product, which has yet to be developed. SERVER-12861 Introduce a maxStalenessMS option when querying secondaries

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-3346 MAX SLAVE LAG - Features to provide a more stable Replication Set under high load

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-25842 Secondary started accepting queries before syncing(replSet still syncing, not yet to minValid optime)

          • Major - P3 - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. SERVER-23892 Do periodic replicated writes every 10 seconds while idle (for maxStalenessMS)

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-4935 Mark node Recovering when replication lag exceeds a configured threshold

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-8858 Extend `isMaster` to return opTime and writeDate

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              misha.tyulenev Misha Tyulenev
              Reporter:
              eliot Eliot Horowitz (Inactive)
              Participants:
              Votes:
              3 Vote for this issue
              Watchers:
              14 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: