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

CollectionRangeDeleter track deletions more reliably

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.5.7
    • 3.5.7
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2017-05-29

    Description

      In current code, each metadata version has provisioned one range to delete when it is retired. Registering a second range would require copying the metadata to a new version (if there is no other event that required the copy), a potentially expensive operation. Keeping a list of ranges for each metadata version would simplify the code and avoid otherwise-unnecessary metadata copying.

      Furthermore, the event-managing code has a race in which a deletion could fail while the requester is not waiting, resulting in the failure not being reported to the requester, and then, possibly, in-migration to a range currently occupied.

      Solving this requires plumbing range deletion event notification through more levels of interface.

      Attachments

        Issue Links

          Activity

            People

              nathan.myers Nathan Myers
              nathan.myers Nathan Myers
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: