Replica set recovery doesn't happen immediately at boot with 3.2 as it did with <3.2

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?