[CONTROLLER-1406] Create a shared akka actor system that can be used by any bundle deployed on the controller Created: 18/Aug/15 Updated: 14/Oct/15 Resolved: 14/Oct/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | Lithium |
| Fix Version/s: | None |
| Type: | Improvement | ||
| 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 |
||
| Description |
|
Currently the remote-rpc-connector and distributed-data-store use akka and each of them create their own actor system. This is not ideal. An actor system comes with it's own overhead of dispatchers and having multiple of them does not help. Furthermore if we had a third module today which needed to use akka we would have to create a 3rd actor system. It would be nice if we move actor system creation to a separate bundle and have rpc and data both use that actor system. |
| Comments |
| Comment by Tom Pantelis [ 14/Oct/15 ] |