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

Better concurrency control on shard metadata refresh

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.12, 3.4.2, 3.5.1
    • Fix Version/s: 3.4.4, 3.5.5
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.4
    • Sprint:
      Sharding 2017-03-27
    • Linked BF Score:
      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

              • Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: