MongoDB | 2656730

Info

In SERVER-79734 we added a check in ReplSetTest.startSet when restart=true that if the caller has not disabled auto-step up behavior but they are using the in-memory storage engine we throw an error. (Without this check, the user would see errors from the subsequent call to replSetStepUp noting the replica set is not yet initialized.) BF-32585 has shown this serverStatus call can race with sharding initialization, however it's not trivial to make this call un-racy in a robust way. For now I think we should remove the check but we can reevaluate if we see a lot of people being confused by the need to set triggerStepUp=false when restarting in a test with the in-memory storage engine in the future.

Top User Comments

xgen-internal-githook commented on Tue, 30 Apr 2024 02:02:55 +0000: Author: {'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'} Message: SERVER-89950 Remove serverStatus call from ReplSetTest.startSet (#21619) (cherry picked from commit ec332a2de3a187d2091f0a99a2d891757f11ee21) GitOrigin-RevId: abf99bf057d7b6cfe834c0b2368647106f047b40 Branch: v8.0 https://github.com/mongodb/mongo/commit/6096cb72e415b0987f85a8af17631cf9ab9a445d xgen-internal-githook commented on Mon, 29 Apr 2024 23:52:29 +0000: Author: {'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'} Message: SERVER-89950 Remove serverStatus call from ReplSetTest.startSet (#21619) GitOrigin-RevId: ec332a2de3a187d2091f0a99a2d891757f11ee21 Branch: master https://github.com/mongodb/mongo/commit/f3bc33bae1b10b73bd45249cf56855454bd7ab36

Steps to Reproduce