[SERVER-37022] TransactionCoordinator should have an additional state for when it has not yet received any event Created: 06/Sep/18 Updated: 04/Oct/18 Resolved: 04/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | ShardedTxn:DistributedCommit, transaction-coordinator-management | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding 2018-10-08 | ||||||||
| Participants: | |||||||||
| Description |
|
In order to validate coordinator creation for a given LSID and transaction number in the presence of retries, if a coordinator exists already for the given LSID and transaction number we need to know whether or not the coordinator is newly initialized and has not yet received any vote. If it has received some vote or the coordinateCommit message, then there must be some programmer error, since we should never try to create a coordinator with an LSID and txn number that already exist. |
| Comments |
| Comment by Matthew Saltz (Inactive) [ 04/Oct/18 ] |
|
This is no longer needed in order to perform this validation, since we'll rely on already existing validation through the coordinator's local participant. |