[SERVER-67428] secondary_dryrun_vote_timeout.js should wait for "Voted for importCollection" log message on the secondary Created: 21/Jun/22  Updated: 29/Oct/23  Resolved: 27/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.1, 6.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-51528 Make secondary import dryRun applicat... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Sprint: Execution Team 2022-07-11
Participants:
Linked BF Score: 2

 Description   

The import collection logic on a secondary communicates its progress to the primary in a thread separate from the oplog application pool. This change was made in SERVER-51528. Occasionally, we have seen the secondary_dryrun_vote_timeout.js test fail because the primary did not receive the vote request from the secondary. We can make this test more robust by making the test wait for the secondary to vote for the import before waiting for acknowledgement on the primary.



 Comments   
Comment by Githook User [ 02/Aug/22 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-67428 secondary_dryrun_vote_timeout.js waits for primary to receive import vote from secondary

(cherry picked from commit f09d4a17cf4ed70b775642656f173b310fd5d3a5)
Branch: v6.0
https://github.com/10gen/mongo-enterprise-modules/commit/a7f2a284a4992be8d2f75750acee64812e1b8c1c

Comment by Githook User [ 27/Jun/22 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-67428 secondary_dryrun_vote_timeout.js waits for primary to receive import vote from secondary
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/f09d4a17cf4ed70b775642656f173b310fd5d3a5

Generated at Thu Feb 08 06:08:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.