[CONTROLLER-1607] Implement agent RPCs for shard leader movement testing Created: 15/Feb/17 Updated: 25/Jul/23 Resolved: 10/Apr/17 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Tomas Cere |
| 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: | 7805 |
| Description |
|
Implement part of RPCs defined in Some scenarios needs control over which cluster member becomes shard leader and when. Currently that would be ll:become-module-leader and ll:become-prefix-leader. |
| Comments |
| Comment by Tomas Cere [ 27/Mar/17 ] |
| Comment by Vratko Polak [ 29/Mar/17 ] |
|
> ll:become-module-leader It seems this would be better implemented as an addition to cluster-admin.yang |
| Comment by Tomas Cere [ 30/Mar/17 ] |
|
leader movement for module based shards in ClusterAdminRpcService |