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

RangeDeleter should log when its about to wait for majority replication

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.14, 3.4.4
    • Fix Version/s: 3.6.4, 3.7.3
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.6, v3.4
    • Epic Link:
    • Sprint:
      Sharding 2017-12-04, Sharding 2018-01-01, Sharding 2017-12-18, Sharding 2018-02-26, Sharding 2018-03-12

      Description

      The RangeDeleter not only deletes the necessary documents, but also waits for a majority of members to be caught up. In 3.4, this happens all the time, whereas in master, this happens only if any documents were deleted.

      In 3.4, the w:majority wait happens after the (apparently final) "rangeDeleter deleted X documents" message, whereas in master, it happens before the final "Deleted X documents in DB.COLL range ..." message.

      This ticket is to request log message(s) (at default level) to indicate when the RangeDeleter is spending time waiting for replication.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-29812 RangeDeleter unnecessarily waits for 'majority' write concern

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

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: