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

Change config.rangeDeletions optional 'pending' flag to required 'readyToDelete'

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding
    • Sharding 2019-12-16

    Description

      Originally we designed the config.rangeDeletions collection to have a 'pending' boolean flag whose presence indicated that the range was not yet ready to delete, and doing an $unset operation on that flag would trigger range deletions. After spending a little time with that implementation it seems like it would make more sense to just have a non-optional flag 'readyToDelete' which is either true or false, and setting the value to true is what triggers deletion.

      We will do this ticket in a final pass after other functionality is in, since this is really just cleanup work.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: