New sessions are asynchronously flushed to disk, so a stepdown immediately after starting a session will cause it to disappear. This is a problem for jscore tests that call startSession and expect the returned sessionId to exist for the rest of the test.

This should not affect the enable_sessions.js override or the tests that use the shell's startSession helper since they create a DriverSession, which lives on the client and should survive failovers.