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

Improve the speed of incremental chunk metadata refresh

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.10, 3.4.0-rc1
    • Component/s: Sharding
    • Labels:
      None

      Initial chunk load, which requires a table scan, is 1.1 seconds:

      2016-10-24T16:18:01.297+0000 I SHARDING [Balancer] ChunkManager: time to load chunks for buildlogs.logs: 1133ms sequenceNumber: 2 version: 157970|1||576339e709168e06c8eb8097 base
      

      Subsequent refreshes, which require a very fast query (0 ms) still take over 250ms:

      2016-10-24T16:33:41.683+0000 I SHARDING [Balancer] ChunkManager: time to load chunks for buildlogs.logs: 264ms sequenceNumber: 3 version: 157970|4||576339e709168e06c8eb8097 based
      

      This issue is to investigate the issue.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            dan@mongodb.com Daniel Pasette (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: