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

ScopedCollectionMetadata compare equal

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.9
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible

      Description

      Killing specific queries that depend on a range that a secondary has been notified is being deleted requires (1) identifying CollectionMetadata instances that have a chunk overlapping it, and (2) invalidating queries that have a ScopedCollectionMetadata that refers to one such instance. For (2), it suffices to provide op== / op!= on ScopedCollectionMetadata.

      Assumption is that most running queries on a collection will seem to depend on any given chunk being removed, and the majority of those will be expected to die, so a scan of all such running queries for each such event is more economical than keeping a list of queries that depend on each CollectionMetadata.

        Attachments

          Activity

            People

            Assignee:
            nathan.myers Nathan Myers
            Reporter:
            nathan.myers Nathan Myers
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: