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

Cache chunk bounds as an array in resharding collection cloning pipeline

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v5.0
    • Sprint:
      Sharding 2021-06-28
    • Story Points:
      1

      Description

      DocumentSourceSequentialDocumentCache::doOptimizeAt() caches on a per-stage basis of the $lookup pipeline. Restructuring the aggregation pipeline so the $objectToArray values are done as a separate stage from the $match that references the $$sk variable would mean their results can be cached too.

      The changes made in this ticket will be obsoleted by SERVER-57667 but will reduce the per-document processing overhead by a constant factor.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-57579 DocumentSourceSequentialCache doesn't clone, ruining non-correlated $lookup pipeline caching in sharded deployments

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-57667 Improve processing speed for resharding's collection cloning pipeline

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-57705 DocumentSourceSequentialCache can wind up in a suboptimal location due to optimizations

          • Major - P3 - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. SERVER-57483 Results from $lookup stage are not cached for a resharding operation's sub-pipeline

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

            Activity

              People

              Assignee:
              max.hirschhorn Max Hirschhorn
              Reporter:
              max.hirschhorn Max Hirschhorn
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: