[CONTROLLER-1006] Clustering : TransactionChain id created by the Clustered Data Store are not unique Created: 08/Nov/14 Updated: 25/Jul/23 Resolved: 15/Nov/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Moiz Raja | Assignee: | Moiz Raja |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||||||
| External issue ID: | 2339 | ||||||||||||||||
| Description |
|
In the CDS the TransactionChainId's are used to by the Shard actor to determine which transaction chain should be used when creating a transaction. If the id is not unique the wrong chain may be used to create the transaction which will break the guarantees that TransactionChains are supposed to provide. Furthermore exceptions may be thrown when creating a transaction on a TransactionChain because the previous transaction may not be in the ready state. |
| Comments |
| Comment by Moiz Raja [ 08/Nov/14 ] |
| Comment by Tom Pantelis [ 08/Nov/14 ] |
|
Cherry pick to stable/helium failed. |
| Comment by Tom Pantelis [ 15/Nov/14 ] |
|
Merged patch https://git.opendaylight.org/gerrit/#/c/12879/ for helium. |