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

Use a fire and forget model when triggering best effort refreshes on create collection path

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v5.0
    • Sprint:
      Sharding EMEA 2021-05-31

      Description

      Currently after committing a new collection to the config server, we are refreshing all the shards with chunks as a best effort so they can warm up their cache. Right now it is done sequentially and waiting for the response for about 30 seconds, however, given the nature of this call, a better approach would be to fire and forget the requests, like this. This would improve the performance of the collection creation, specially in large clusters with a lot of chunks where the optimized path was taken.

        Attachments

          Activity

            People

            Assignee:
            marcos.grillo Marcos José Grillo Ramirez
            Reporter:
            marcos.grillo Marcos José Grillo Ramirez
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: