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

Reduce OplogFetcher getMore awaitData timeout for nodes in RollbackTest fixture

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.3
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2, v4.0
    • Sprint:
      Repl 2020-01-27

      Description

      SERVER-37390 made it so that the RollbackTest fixture uses a high election timeout (24 hours) to prevent unplanned state transitions during test execution. This has the unintended side effect of slowing down tests that use this fixture since the awaitData timeout on getMores sent by the OplogFetcher are affected by the election timeout. A 24 hour election timeout causes us to use the maximum awaitData timeout which is 30 seconds. When we stop replication throughout the RollbackTest, this can cause delays when we wait for the stopReplProducer failpoint to be hit, since a getMore doesn't time out and return to the syncing node for 30 seconds even if there is no data to fetch. We can reduce this timeout inside RollbackTest by using this existing failpoint.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ryan.timmons Ryan Timmons
              Reporter:
              william.schultz William Schultz (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: