[CONTROLLER-743] Clustering : Use protobuf serialization in remoterpc connector Created: 27/Aug/14 Updated: 17/Nov/15 Resolved: 17/Nov/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | Post-Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Abhishek Kumar | Assignee: | Muthukumaran Kothandaraman |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| External issue ID: | 1638 |
| Priority: | Low |
| Description |
|
sal-remoterpc-connector module uses Akka's default java serialization for message passing across nodes in cluster. For better efficiency, it should be changed to protobuf. Similar work has been done in sal-distributed-datastore. |
| Comments |
| Comment by Moiz Raja [ 18/Aug/15 ] |
|
Distributed Data Store has switched to using java externalizable to serialize messages as creating protobuff messages takes up a lot of memory (even though the message on the wire is small). |
| Comment by Moiz Raja [ 17/Nov/15 ] |
|
There is no need to fix this - we have decided to not use protobuf in CDS so there no point in implementing it for Notification Broker. |