[SERVER-14486] Increase unit test coverage around applying updates to a doc that needs to be refetched from the sync source Created: 07/Jul/14 Updated: 06/Dec/22 Resolved: 07/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Dannenberg | Assignee: | Backlog - Replication Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
Original ticket title: "replace ReplSetTest::TestInitApplyOp2" runs a multiInitialSyncApply with the first arg as an update oplog entry and SyncTest2 as the second, which inserts the base object of the update from arg one when shouldRetry is ran (so the document appears between the failing to apply the first time and retrying) original test: https://github.com/mongodb/mongo/commit/1e4a71eb26808a828fff29ada663a7c43e0bdd9f |
| Comments |
| Comment by Eric Milkie [ 03/Sep/15 ] |
|
This is still something we need test coverage for. |