Info

In the function stopReplicationAndEnforceNewPrimaryToCatchUp() still has the problem listed in SERVER-59796. We need to make sure that the secondaries are actually caught up (which may be impossible, since the primary's PrimaryOnlyService may write at any point meaning the secondaries won't be caught up), or we need to make the "candidate secondary", the secondary that is passed in to the function to be made the new primary, ahead of the other secondary so that it wins the election. One way I can think of performing the latter idea is to stop replication on the other secondaries and not on the candidate secondary. We can then perform a write on the primary and make sure that it has reached the candidate secondary. This will ensure that the candidate secondary is more up-to-date than any other secondary, and then it can win the election.

Top User Comments

xgen-internal-githook commented on Fri, 10 Nov 2023 22:05:46 +0000: Author: {'name': 'kauboy26', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'} Message: SERVER-81591 synchronize step up for PrimaryOnlyService in stopReplicationAndEnforceNewPrimaryToCatchUp Branch: v7.1 https://github.com/mongodb/mongo/commit/f4b1d3c5e7e5e7a51a9fb7d7bd8cd5c796b73137 xgen-internal-githook commented on Fri, 10 Nov 2023 22:00:33 +0000: Author: {'name': 'kauboy26', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'} Message: SERVER-81591 synchronize step up for PrimaryOnlyService in stopReplicationAndEnforceNewPrimaryToCatchUp Branch: v7.0 https://github.com/mongodb/mongo/commit/7299da37905359366dfd485b1f59dc04574bc3ff xgen-internal-githook commented on Fri, 20 Oct 2023 20:49:25 +0000: Author: {'name': 'kauboy26', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'} Message: SERVER-81591 synchronize step up for PrimaryOnlyService in stopReplicationAndEnforceNewPrimaryToCatchUp Branch: master https://github.com/mongodb/mongo/commit/aa376b22b5d686fcca6cfdbd0f247529d1f9283f

Steps to Reproduce