[SERVER-45641] Tag awaitdata_getmore_new_last_committed_optime.js requires_snapshot_read Created: 17/Jan/20 Updated: 29/Oct/23 Resolved: 18/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Task | 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 | ||||
| Sprint: | Repl 2020-01-27 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The test runs a secondary read (getMore) that is blocked on a failpoint while waiting for replication. On ephemeralForTest, secondary reads hold the PBWM lock which would block secondary oplog application. The purpose of the test is to test exhaust cursor behaviors and I dont think it adds any value testing that under ephemeralForTest. So I think we can tag the test requires_snapshot_read. This is because we don't hold PBWM lock for secondary reads when the storage engine supports snapshot reads. |
| Comments |
| Comment by Githook User [ 18/Jan/20 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |