[CONTROLLER-1533] Global MD-SAL RPCs are not global Created: 29/Jul/16 Updated: 25/Jul/23 Resolved: 12/Oct/16 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jan Medved | Assignee: | Unassigned |
| Resolution: | Duplicate | 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: | 6310 | ||||||||
| Description |
|
The MD-SAL Global RPCs are supposed to be global, similar to routed RPCs. That means, a client running on one node in the cluster should be able to invoke a global RPC implementation on another node in the cluster. However, the current implementation is local-only, the entries for registered Global RPC implementations are not being propagated beyond a node. This needs to be fixed, along with the Notifications - where the scope is also supposed to be global. This bug is for Born, but i don't see an option to enter Boron or 0.5.0 in the version field. |
| Comments |
| Comment by Colin Dixon [ 02/Aug/16 ] |
|
Per Robert and Colin, the RPC probably needs to be substantially reworked beyond just this bug. We can probably make it work the same as routed RPCs without too much effort. There is a patch related to BUG-3128 (a dupe of this) that might be useful. That being said, this should not be considered a blocker for Boron. |