[SERVER-78023] Make query_oplogreplay.js test more stable by accounting for oplog entries from background processes Created: 13/Jun/23 Updated: 29/Oct/23 Resolved: 14/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ivan Fefer | Assignee: | Ivan Fefer |
| 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: | QE 2023-06-26 | ||||
| Participants: | |||||
| Linked BF Score: | 35 | ||||
| Description |
|
Test query_oplogreplay.js can fail in rare cases when oplog entries from background processes (for example, index build on some system collection) are intertwined with test oplog entries, messing up totalDocsExamined execution stat. To fix it, we should raise the allowed totalDocsExamined, but still keep it low to assert that there where no full oplog collection scan. |
| Comments |
| Comment by Githook User [ 14/Jun/23 ] |
|
Author: {'name': 'Ivan Fefer', 'email': 'ivan.fefer@mongodb.com', 'username': 'Fefer-Ivan'}Message: |