[SERVER-40457] test that secondaries roll over their oplogs when they exceed oplogSize Created: 03/Apr/19 Updated: 29/Oct/23 Resolved: 23/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | prepare_testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2019-04-22, Repl 2019-05-06 | ||||||||
| Participants: | |||||||||
| Description |
|
In the absence of transactions, we don't have testing that secondaries roll over their oplogs when they exceed oplogSize. This is specifically to test that work in This can likely be built on top of initial_sync_oplog_rollover.js or the tests added in |
| Comments |
| Comment by Githook User [ 23/Apr/19 ] |
|
Author: {'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng', 'username': 'ldennis'}Message: |
| Comment by Judah Schvimer [ 10/Apr/19 ] |
|
We would like to add a test that does not use transactions to both test that behavior explicitly, and allow it to be run on other storage engines that do not support transactions (in-memory most notably). This test can likely be incredibly similar to one introduced by |
| Comment by Lingzhi Deng [ 10/Apr/19 ] |
|
It looks like tests added by |