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

Validate and/or fix invariant in MetadataManager::cleanUpRange

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Sharding 2019-12-02, Sharding 2019-12-30, Sharding 2020-01-13, Sharding 2020-01-27

      Description

      This invariant to check that the metadata has not been cleared when calling cleanUpRange may not be valid. It seems that it would be possible to hit this invariant with this existing use of cleanUpRange, in the case where the collection gets dropped and a refresh occurs after the migration completes but before cleanUpRange is called here. It will also be possible to hit this invariant with the addition of new code in the resumable range deleter project.

      We should verify whether this should truly be an invariant and:

      • If so, fix the existing bugs around usages of cleanUpRange
      • If not, change the invariant to an error or otherwise handle this case appropriately.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matthew.saltz Matthew Saltz
              Reporter:
              matthew.saltz Matthew Saltz
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: