ID | IEP-81 |
Author | |
Sponsor | |
Created |
|
Status | DRAFT |
The IEP is intended to eliminate all the current limitations with cluster management and provide additional features which may be available out of the box.
All of Ignite Cluster management operations are presented as running compute tasks over the cluster. Depending on the management operation required to be executed some of the tasks are running on a single Ignite node only or performing full compute operation overall cluster nodes with reducing the computation result on the originating node.
For instance, single-node operations may look the following:
Distributed management compute tasks may look the following:
Each time a new management task is added or is required to be added the developer should take into account the following things:
Without handlers and abstractions mentioned above, a new management task won't be available for a user even if it persists in the node classpath (it's still possible to run it using the ignite thin client). Most of such handlers and abstractions look like a boilerplate code and must be covered by some internal command exposer.
Command Plugin Extension
Ignite plugins have no control over the cluster management operations. The built-in management tasks can't be extended by Ignite running with custom plugins and even more, they can't be available through the standard Ignite's REST, JMX, CLI APIs.
Ignite CLI uses under the hood its own internal communication protocol so-called Binary Rest Protocol which enables CLI tools to communicate with the existing Ignite cluster and run some compute tasks, perform cache operation, as well as has listeners of topology changes. An instance of the GridClient started each time a new management operation executes the same way as an instance of IgniteClient can do which in turn is a part of the official Ignite Binary Protocol. Taking into account that the Binary Rest Protocol which is used for the CLI tool fully undocumented looks like
Ignite has some management tasks that don't obey the role model controlled by SecurityManager and has different execution flow depending on which execution context is set. For instance:
All of the issues above require management tasks to be always being executed in the same manner with the same security context.
The following design issues bases on current management task implementation are present:
The following new features can be available out of the box with minimal additional source code changes:
// Provide the design of the solution.
// Provide the implementation phases.
// Describe project risks, such as API or binary compatibility issues, major protocol changes, etc.
// Links to discussions on the devlist, if applicable.
[1] https://www.mail-archive.com/dev@ignite.apache.org/msg49612.html