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

Make timeseries-movechunk FSM workloads more resilient to timeouts

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 200

      These particular FSM workloads run more slowly, leading to many timeout-related failures.

      There exist server parameters that can increase timeouts for specific phases of migration , like waiting for range deletion on the recipient. We already increase the range deletion wait timeout to five minutes on config fuzzers, which doesn't seem to be sufficient according to current BFs.

      We can also allow retries on moveChunks that fail due to timing issues on slower FSM workloads as well.

            Assignee:
            Unassigned Unassigned
            Reporter:
            blake.oler@mongodb.com Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: