[CONTROLLER-981] Clustering : TransactionProxy should support the ability to accept a local ThreePhaseCommitCohort actor path for forward compatibility Created: 02/Nov/14  Updated: 25/Jul/23  Resolved: 03/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
Platform: All

External issue ID: 2296

 Description   

In Helium when the ShardTransaction processes a Ready message it sends back a the path of a ThreePhaseCommitCohort actor in the ReadyReply. This path is actually a local actor path, this local actor path is then converted into a remote path by the TransactionProxy.

The fix for CONTROLLER-720 breaks this capability which is required to support forward compatibility in a cluster where a transaction request originates in a node that has been upgraded to Helium-1 and the actual transaction is happening on a node which has not yet been upgraded to Helium-1.

 Comments   
Comment by Moiz Raja [ 02/Nov/14 ]

https://git.opendaylight.org/gerrit/12450

Generated at Wed Feb 07 19:54:22 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.