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

RangeDeleter should log when its about to wait for majority replication

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.4, 3.7.3
    • Affects Version/s: 3.2.14, 3.4.4
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • v3.6, v3.4
    • Sharding 2017-12-04, Sharding 2018-01-01, Sharding 2017-12-18, Sharding 2018-02-26, Sharding 2018-03-12

      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.

            kevin.pulo@mongodb.com Kevin Pulo
            kevin.pulo@mongodb.com Kevin Pulo
            0 Vote for this issue
            6 Start watching this issue