We have an Automation Agent test that fires up a four-node replica set, takes down one secondary and the primary, and waits for the two remaining nodes to report accurate information via rs.status(). This test is failing on Windows, timing out because the two remaining nodes continue to report that the primary is healthy, which can by seen by connecting to them via the Mongo shell and running rs.status(). I have not been able to reproduce this outside the test, and the test passes on Linux and OS X, leading me to believe that there may be some sort of Windows-specific race condition. Memory dumps from the two remaining secondaries are attached.

CC mark.benvenuto