In a mongosync BF in a v5.0 kill sharded suite I'm investigating, the progress endpoint times out after 30 seconds. This happens because the primary is killed, and a secondary fails to start up (taking a full 30 seconds waiting for the result of an election). The old primary had been killed, so it doesn't get the vote from that one, but from the other secondary it gets no response after 30 seconds (but it waits!). You can see this behavior here.

Since both the testing fixture waiting on the progress endpoint times out after 30 seconds, and the secondary up for election waits for a response for 30 seconds, this causes the problem. Is there a way for me to configure a parameter so that the election will fail after less than 30 seconds have elapsed?