[SERVER-42341] Make checks more specific in log_secondary_oplog_application.js Created: 22/Jul/19 Updated: 29/Oct/23 Resolved: 23/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vesselina Ratcheva (Inactive) | Assignee: | Vesselina Ratcheva (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Minor Change | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2019-07-29 | ||||
| Participants: | |||||
| Linked BF Score: | 10 | ||||
| Description |
|
The test needs to check whether ops are logged as slow or not. It assumes that its inserts are the only source of crud ops, which is incorrect in the face of HMAC key insertions. The checkLog statements need to be changed to target the exact contents of the inserts (which are already unique) instead of crud ops. |
| Comments |
| Comment by Githook User [ 23/Jul/19 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: |