[CONTROLLER-913] Clustering : When a transaction is local then do not serialize the Reading/Writing of data Created: 02/Oct/14 Updated: 15/Nov/14 Resolved: 15/Nov/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Moiz Raja | Assignee: | Kamal Rameshan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2136 |
| Description |
|
When reading/writing data in a transaction the Clustered Data Store converts a NormalizedNode to a Protocol Buffer message regardless of whether the transaction is done with a local shard or a remote shard. As a performance optimization we need to avoid serialization of NormalizedNode when doing local transactions. |
| Comments |
| Comment by Moiz Raja [ 11/Nov/14 ] |
|
A bug was found with the previous fix where when the path of the actor was local the code did not recognize it and as such considered the path to be removed. If the path is considered remote then we serialize so in some cases we were not doing the right thing. Fix for the local path issue here -> https://git.opendaylight.org/gerrit/#/c/12700/ |
| Comment by Moiz Raja [ 15/Nov/14 ] |
|
Merged to stable/helium |