[SERVER-48954] Make replication_recovery_test handle doc-level locking storage engine Created: 18/Jun/20 Updated: 29/Oct/23 Resolved: 23/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Henrik Edin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2020-06-29 |
| Participants: |
| Description |
|
Multiple tests in replication_recovery_test.cpp check for which order the oplog applier applies them. When using a storage engine that does not support document-level locking the ordering is guaranteed because all jobs get scheduled on the same replication writer thread because the '_id' field is not used when dispatching the jobs. See this code: We should fix these tests so they don't assume this order. |
| Comments |
| Comment by Githook User [ 22/Jun/20 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: |