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

Only wait for replication once at the end of range deletion

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding 2020-02-24
    • 0

      We now wait for replication after each batch of documents deleted, instead of once at the end, as we did in 4.2. This was done intentionally knowing that deletion would be delayed some with the benefit of simplifying the deleter logic, but on second thought it doesn't simplify much and we think it's better to just do it once at the end, so we should do that.

            Assignee:
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Reporter:
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: