[SERVER-36398] Use anonymous uassert code when startTransaction=true is specified for prepareTransaction Created: 01/Aug/18 Updated: 06/Dec/22 Resolved: 17/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | prepare_errors, prepare_optional | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
We currently return ConflictingOperationInProgress. |
| Comments |
| Comment by Samyukta Lanka [ 02/Aug/18 ] |
|
Holding off on doing this for now because it isn't as simple a change as originally thought. This change would need to happen in _beginOrContinueTxn because that's where we currently uassert with ConflictingOperationInProgress if startTransaction is provided. Since we don't have any notion of which operation called _beginOrContinueTxn, we'd have to also change to an anonymous error code for operations that aren't prepareTransaction which is undesirable. I'm looking into whether we can validate function arguments earlier than _beginOrContinueTxn. |