[SERVER-41008] Check lastCommittedOpTime instead of awaitReplication for prepare recovery/index build tests Created: 03/May/19 Updated: 29/Oct/23 Resolved: 09/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | Repl 2019-05-20 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 12 | ||||||||||||||||||||
| Description |
|
recover_prepared_transactions_startup_secondary_application.js and prepare_transaction_index_build.js need to use PrepareHelpers.prepareTransaction with w: 1 to test prepare recovery/index build blocking prepared transactions on secondaries. Instead of using awaitReplication which doesn't necessarily align with the primary's local view of majority committed point, we should check lastCommittedOpTime on primary to make sure the majority commit point has been advanced past the prepareTimstamp. |
| Comments |
| Comment by Githook User [ 24/May/19 ] |
|
Author: {'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng', 'username': 'ldennis'}Message: |
| Comment by Githook User [ 09/May/19 ] |
|
Author: {'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng', 'username': 'ldennis'}Message: Branch: master |