Add backoff to batch_write_exec when retrying with no progress made

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • ClusterScalability Mar17-Mar31
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Originally, this ticket was to increase the allowed number of rounds without progress in debug builds. The original description is maintained below. Now, this ticket is to instead add a backoff in between retries when progress is not made. The hope is that the backoff will make the existing number of retries more effective, such that we don't need to add special tweaks for slower variants.


      SERVER-93898 made a very similar change, but only increased the limit in sanitizer builds. BF-36195 observed a failure, apparently due to slowness, on a windows debug build (which is known to be slow). We should raise the maxRoundsWithoutProgressParameter at least on all debug builds, but should also consider just raising it for all resharding tests so we don't need to keep adding classes of slow variants here.

            Assignee:
            Brett Nawrocki
            Reporter:
            Brett Nawrocki
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: