[SERVER-42076] Do not skip validation in jstests that shutdown with prepared transactions Created: 03/Jul/19 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Vesselina Ratcheva (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
We have a number of jstests that leave prepared transactions open when stopping the set. They would have to skip collection validation, as it was known to encounter prepare conflicts. After |
| Comments |
| Comment by Vesselina Ratcheva (Inactive) [ 03/Jul/19 ] |
|
Actually, even after that fix we would only be able to run validate on secondaries, which limits the utility of this work. On primaries, the validate command will not be able to acquire the collection X lock because of the prepared transaction. |