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

[v3.2] Increase awaitSecondary timeout in initial_sync_cloner_dups.js to at least 10 minutes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 3.2.13
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL
    • Backport Requested:
      v3.0
    • Linked BF Score:
      0

      Description

      The initial_sync_cloner_dups.js test waits for a secondary node to complete initial sync here, but there have been instances, such as in BF-5576 of this initial sync taking longer than the prescribed timeout of 2 minutes, due to slow mmap flushing. These timeouts should be increased to at least 10 minutes to account for these kinds of scenarios.

      This only applies to 3.2, since later versions of this test just use the default timeout of replsettest.js

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              william.schultz William Schultz (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: