Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
4.2.17
-
None
-
ALL
-
Sharding 2021-10-18, Sharding 2021-11-01
-
0
Description
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:
- The `replSetStepDown: 300` command might be blocking the former primary re-election for too long. Perhaps try the timeout of 60 or 100
- 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.