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

Ensure refresh performance is not affected by sharded catalog index refresh

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • Sharding EMEA
    • Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06

    Description

      The normal refresh scenario should not be affected by changes for PM-1965, a regular incremental refresh due to stale data placement data should not incur in extra latency due to the presence of indexes in the sharded index catalog. The outcome of this ticket should be a measurement of the behavior of refreshes before and after the catalog cache changes, in order to ensure we're not penalizing regular collections operation due to the new refresh scheme.

      Attachments

        Activity

          People

            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: