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

Relax timings in change_stream_shard_failover to make it less flaky

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.2.17
    • Component/s: None
    • ALL
    • Sharding 2021-10-18, Sharding 2021-11-01
    • 0

      I don't see any actual failure in the logs of failed change_stream_shard_failover.js test except it spends too much time in some of the steps:

      1. The `replSetStepDown: 300` command might be blocking the former primary re-election for too long. Perhaps try the timeout of 60 or 100
      2. The `awaitNodesAgreeOnPrimary()` default timeout is 10 minutes. Perhaps wait for some smaller timeout. I see in the logs this step sometimes takes too long, maybe because of #1

      I would also add better logging around those cases.

            Assignee:
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            Reporter:
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: