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

Reshard cloner inserts gets slower as output collection gets larger

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • None
    • Sharding NYC

    Description

      Whatever improvement we decide to do, we should take into consideration whether we want to keep resumability.

      I also expect that the global index cloner would behave similarly.

      Attachments

        Issue Links

          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-72044 Make reshard collection cloner run fetch and insert independently

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-72045 Make global index cloner run fetch and insert independently

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-72674 Investigate global index cloner insert performance for 1TB collections

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

          Activity

            People

              backlog-server-sharding-nyc Backlog - Sharding NYC
              randolph@mongodb.com Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: