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

Better concurrency control on shard metadata refresh

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.2.12, 3.4.2, 3.5.1
    • 3.4.4, 3.5.5
    • Sharding
    • None
    • Fully Compatible
    • v3.4
    • Sharding 2017-03-27
    • 0

    Description

      Currently, the shard limits the number of threads refreshing the config metadata here. This limit is very crude and does not differentiate refresh for different namespaces. It is possible that the all the ticket holders are trying to refresh the same collection. In this case, it limits parallelism while doing wasted work.

      Attachments

        Issue Links

          Activity

            People

              kaloian.manassiev@mongodb.com Kaloian Manassiev
              randolph@mongodb.com Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: