[SERVER-40468] Allow RollbackTest fixture to skip collection validation when restarting node Created: 04/Apr/19 Updated: 29/Oct/23 Resolved: 03/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Robert Guo (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | STM 2019-05-20 | ||||||||
| Participants: | |||||||||
| Story Points: | 1 | ||||||||
| Description |
|
The validate command requires a collection X lock, which cannot be acquired if there are outstanding transactions running on the server. The rollback fuzzer may attempt to call RollbackTest#restartNode() after having started transactions on the server. The RollbackTest#restartNode() method should therefore take an optional skipValidation boolean and pass it through to the rst.stop() call. The RollbackTest#transitionToSteadyStateOperations() method should also be updated to take an optional skipDataConsistencyChecks boolean (wrapped in an object so it's effectively a named parameter) that acts as a syntactic alternative to the usage of expectPreparedTxnsDuringRollback as a way to avoid calling checkDataConsistency(). |
| Comments |
| Comment by Githook User [ 03/May/19 ] |
|
Author: {'name': 'Robert Guo', 'username': 'guoyr', 'email': 'robertguo@me.com'}Message: |