[SERVER-41718] recover_prepared_transactions_startup_secondary_application.js should wait for node to be in the secondary state before reading from it Created: 13/Jun/19  Updated: 29/Oct/23  Resolved: 14/Jun/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.2.0-rc3, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-42171 Race in recover_prepared_transactions... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Repl 2019-06-17, Repl 2019-07-01
Participants:
Linked BF Score: 20

 Description   

recover_prepared_transactions_startup_secondary_application.js waits for all writes before the nodes went into recovery to be majority committed, but it doesn't wait for the node to transition back into the secondary state. This can cause a test to fail if the node has reconstructed these prepared transactions (and thus cause the majority commit point to advance), but hasn't exited recovering mode.



 Comments   
Comment by Githook User [ 02/Jul/19 ]

Author:

{'name': 'Samy Lanka', 'username': 'lankas', 'email': 'samy.lanka@mongodb.com'}

Message: SERVER-41718 recover_prepared_transactions_startup_secondary_application.js waits until node enters secondary state before reading from it

(cherry picked from commit dc9a28bff8ee8e20f764839f52172c458b24dbac)
Branch: v4.2
https://github.com/mongodb/mongo/commit/c27638adedd3fbac4d560cc2be466c8fa2ddf314

Comment by Githook User [ 14/Jun/19 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-41718 recover_prepared_transactions_startup_secondary_application.js waits until node enters secondary state before reading from it
Branch: master
https://github.com/mongodb/mongo/commit/dc9a28bff8ee8e20f764839f52172c458b24dbac

Generated at Thu Feb 08 04:58:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.