Mikhail Pochatkin created IGNITE-19522:
------------------------------------------
Summary: Modify deploy unit command
Key: IGNITE-19522
URL: https://issues.apache.org/jira/browse/IGNITE-19522
Project: Ignite
Issue Type: New Feature
Components: cli, rest
Reporter: Mikhail Pochatkin
ignite3 unit deploy <deployment_unit_id> --version (-uv)
<deployment_unit_version> --path (-up) <file>|<dir> [--nodes
MAJORITY|ALL|<nodes>]
Options:
* --version -uv - defines the deployment unit’s version
(<deployment_unit_version>).
* --path -up - path to JAR-file (<file>) or to the directory (<dir>) which
contains all required class files and resources.
* --nodes - defines the set of target nodes where the deployment unit will be
deployed. The possible options are possible:
* MAJORITY - Default value. The CMG majority nodes will be chosen as the
target nodes (including the leader node).
* ALL - All available nodes will be chosen as the target nodes. In this case
“available” means The CMG majority nodes (see MAJORITY option) and all nodes
that will be live during the deployment process. If some node will go offline
(excluding the CMG majority nodes) then this node will not finish the
deployment process and will request deployment on-demand.
* <nodes> - All nodes with corresponding consistent IDs in form <node_id1[,
node_id2, …]>. Note, that these nodes are treated as an addition to the CMG
majority nodes and behavior is similar to the ALL option (the deployment unit
will be deployed only on available nodes).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
