-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.2.4
-
Component/s: Replication
-
None
-
ALL
-
Had to recover an instance today that was previously the primary in a replica set (2+arb). Followed the same procedure that I've used in past with lightly loaded instances - started with an empty data directory.
In the past, this would immediately start recovering from the standby instance. With this current 3.2.4 deployment, it sat there for a bit over 3 minutes before it started recovery/rebuild process.
Is that expected with 3.2 or some new tuning parameter?
- duplicates
-
SERVER-24058 Connection pool asio doesn't honor setup timeouts
- Closed