...
It's possible to instantiate network manager when local configuration manager with vault underneath it is ready.
Code Block | ||||
---|---|---|---|---|
| ||||
NetworkView netConfigurationView = locConfigurationMgr.configurationRegistry().getConfiguration(NetworkConfiguration.KEY).value(); // Network startup. Network net = new Network( new ScaleCubeNetworkClusterFactory( localMemberName, netConfigurationView.port(), Arrays.asList(netConfigurationView.networkMembersNames()), new ScaleCubeMemberResolver())); NetworkCluster netMember = net.start(); |
...
At this point it's possible to start business logic components like Baseline Manager, Affinity Manager, Schema Manager and Table Manager. Exact The exact set of such components it is undefined.
Code Block | ||||
---|---|---|---|---|
| ||||
// Baseline manager startup. BaselineManager baselineMgr = new BaselineManager(configurationMgr, metaStorageMgr, netMember); // Affinity manager startup. AffinityManager affinityMgr = new AffinityManager(configurationMgr, metaStorageMgr, baselineMgr); SchemaManager schemaManager = new SchemaManager(configurationMgr); // Distributed table manager startup. TableManager distributedTblMgr = new TableManagerImpl( configurationMgr, netMember, metaStorageMgr, affinityMgr, schemaManager); // Rest manager also goes here. |
...
Manager | Depends On | Used By |
---|---|---|
BaselineManager |
| AffinityManager in order to retrieve the current baseline. |
AffinityManager |
| TableManager strictly or indirectly through corresponding private distributed affinityAssignment key. |
SchemaManager |
| TableManager in order to handle corresponding schema changes. |
TableManager |
| IgniteImpl |
...
Finally, it's possible to deploy registered watches and create IgniteImpl that will inject top-level managers in order to provide table and data manipulation logic to the user.
...