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

Collection chunk loading is aborted entirely if fetching all the chunks takes more than 30 seconds

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0, 4.2.19, 4.0.29, 4.4.13
    • Affects Version/s: 3.6.17, 4.2.4, 4.0.17
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2, v4.0
    • Sharding 2020-06-01

      The collection chunk loading code uses the _exhaustiveFindOnConfig call, which applies 30 seconds of timeout to the entire fetch (not just the individual getMore invocations).

      If there is a large number of chunks and the config server fetches take more than 30 seconds in total, the initial chunk loading will never succeed, because each attempt will fail with ExceededTimeLimit and will throw out whatever data was partially loaded on the previous attempt, thus effectively starting from the beginning.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: