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

Do periodic replicated writes every 10 seconds while idle (for maxStalenessMS)

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.3.12
    • Replication
    • None
    • Fully Compatible
    • Sharding 18 (08/05/16), Sharding 2016-08-29, Sharding 2016-09-19
    • 0

    Description

      For the upcoming maxStalenessMS read preference it is required that periodically there needs to be a replicated write - so it would have a new oplog entry to move forward the OpTime reported to clients.

      These no-op 'n' writes should only be done on the primary when no other replicated writes have been done in the timeout period.

      A side-effect of this will be that an idle replica set will no longer be idle with respect to writes, since it will internally force a write periodically. This new behavior (which also exists in master-slave replication) will show up in things like the calculation of "replication lag" never exceeding a second or two on caught up nodes – previously a lack of writes for a few minutes would immediately show a lag of that period as the new write comes in until it is replicated.

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. SERVER-23893 Increment maxWireVersion for maxStalenessMS

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-4936 Server support for "maxStalenessMS" read preference option

          • 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
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-23908 MMAPv1 DurableImpl::waitUntilDurable should yield the flush lock

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-30339 Enabling profiling and read concern majority with a workload of reads and no writes causes accumulation of dirty data

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-29802 Non-atomic applyOps command should not take out a global exclusive lock

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: