[SERVER-37023] Add BSONObj max size idempotency testing during initial sync and recovery for transactions Created: 06/Sep/18 Updated: 29/Oct/23 Resolved: 03/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Samyukta Lanka |
| 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-03-25, Repl 2019-04-08 | ||||||||
| Participants: | |||||||||
| Description |
|
During initial sync and replication recovery it is possible to hit BSONObj max size exceeded errors due to replaying transactions. We should test that these errors are handled gracefully and do not cause the server to fail recovery. |
| Comments |
| Comment by Githook User [ 03/Apr/19 ] |
|
Author: {'email': 'samy.lanka@mongodb.com', 'name': 'Samy Lanka', 'username': 'lankas'}Message: |
| Comment by Pavithra Vetriselvan [ 26/Feb/19 ] |
|
We've also added commit_transaction_rollback_recovery_data_already_applied.js as a part of |
| Comment by Samyukta Lanka [ 21/Feb/19 ] |
|
judah.schvimer, we don't have testing for this in initial sync yet, but that can happen as part of this ticket |
| Comment by Judah Schvimer [ 21/Feb/19 ] |
|
samy.lanka and pavithra.vetriselvan, what more is left to do on this ticket after tests like commit_transaction_recovery_data_already_applied.js? Do we have testing like this for initial sync? |