Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13659

Investigate changes in SERVER-26755: Collection chunk loading is aborted entirely if fetching all the chunks takes more than 30 seconds

      Description

      Downstream Change Summary

      This ticket adds a startup and runtime server parameter "findChunksOnConfigTimeoutMS" (default 900000) which corresponds to the timeout in milliseconds for find operations against config.chunks.

      Description of Linked Ticket

      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.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            Assignee:
            naomi.pentrel@mongodb.com Naomi Pentrel (Inactive)
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              2 years, 44 weeks, 1 day ago