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

Fix how SBE plan cache deals with ShardFilterer

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • QO 2022-01-10, QO 2022-01-24, QO 2022-02-07, QO 2022-02-21

      A ShardFilterer owns a ScopedCollectionFilter which represents a snapshot in time of parts of sharding state. SBE plans make an owned ShardFilterer if needed, and currently the ShardFilterer will be stored together with the SBE plan in the SBE plan cache. Next time when the cached SBE plan is recovered from the cache we could end up using a stale ShardFilterer.  This ticket is to investigate whether we should or should not store the ShardFilterer in the SBE plan cache.

        1. sbe_plan_cache_blocks_range_deletion.patch
          1 kB

            Assignee:
            ruoxin.xu@mongodb.com Ruoxin Xu
            Reporter:
            ruoxin.xu@mongodb.com Ruoxin Xu
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: