[SERVER-41284] Add failpoint to surface idempotency issues of transaction operations in initial sync Created: 22/May/19 Updated: 29/Oct/23 Resolved: 26/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc5, 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Medha Potluri (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||||||
| Sprint: | Repl 2019-06-17, Repl 2019-07-01, Repl 2019-07-15, Repl 2019-07-29, Repl 2019-08-12 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We should be able to handle all idempotency issues when applying transaction operations during initial sync instead of relying on restarting initial sync. However, due to known idempotency issues for other cases, we have to allow multiple initial sync attempts in initial sync fuzzer test. That will mask unexpected failures of transaction operations. We will add a failpoint to fassert if idempotency issues happen on transaction operations, so that initial sync fuzzer can turn it on and expose such failures. |
| Comments |
| Comment by Githook User [ 26/Jul/19 ] |
|
Author: {'name': 'Medha Potluri', 'email': 'medha.potluri@mongodb.com'}Message: (cherry picked from commit ce1e63a5a7487531f0f53ec1b5570fd49d222dec) |
| Comment by Githook User [ 26/Jul/19 ] |
|
Author: {'name': 'Medha Potluri', 'email': 'medha.potluri@mongodb.com'}Message: |
| Comment by Medha Potluri (Inactive) [ 25/Jul/19 ] |
|
Code review url: https://mongodbcr.appspot.com/488410043/ |