Skip to content

Commit 0753f66

Browse files
committed
IGNITE-24430 Added documentation about migration of the control utility to the thin client protocol (#11856)
Co-authored-by: SofiaSedova <[email protected]> (cherry picked from commit d25afae)
1 parent d53d454 commit 0753f66

File tree

1 file changed

+103
-5
lines changed

1 file changed

+103
-5
lines changed

docs/_docs/tools/control-script.adoc

+103-5
Original file line numberDiff line numberDiff line change
@@ -36,17 +36,16 @@ control.bat <connection parameters> <command> <arguments>
3636

3737
== Connecting to Cluster
3838

39-
When executed without connection parameters, the control script tries to connect to a node running on localhost (`localhost:11211`).
39+
NOTE: Starting from Apache Ignite version 2.17, the utility by default uses a connection through the thin client protocol (configured on a node via `org.apache.ignite.configuration.ClientConnectorConfiguration`). See link:#migration-to-the-thin-client-protocol[Migration Notes] for more information.
40+
41+
When executed without connection parameters, the control script tries to connect to a node running on localhost (`localhost:10800`).
4042
If you want to connect to a node that is running on a remove machine, specify the connection parameters.
4143

4244
[cols="2,3,1",opts="header"]
4345
|===
4446
|Parameter | Description | Default Value
45-
4647
| --host HOST_OR_IP | The host name or IP address of the node. | `localhost`
47-
48-
| --port PORT | The port to connect to. | `11211`
49-
48+
| --port PORT | The port to connect to. | `10800`
5049
| --user USER | The user name. |
5150
| --password PASSWORD |The user password. |
5251
| --ping-interval PING_INTERVAL | The ping interval. | 5000
@@ -63,6 +62,105 @@ If you want to connect to a node that is running on a remove machine, specify th
6362
| --ssl-factory SSL_FACTORY_PATH | Custom SSL factory Spring xml file path. |
6463
|===
6564

65+
== Migration to the thin client protocol
66+
67+
With the default configuration of Ignite, no migration actions will be required. Additional configuration of the connector is no longer necessary.
68+
69+
If you connect to the wrong connector, you will receive an error and may see the message:
70+
71+
`Make sure you are connecting to the client connector (configured on a node via 'org.apache.ignite.configuration.ClientConnectorConfiguration'). Connection to the REST connector was deprecated and will be removed for the control utility in future releases. Set up the 'IGNITE_CONTROL_UTILITY_USE_CONNECTOR_CONNECTION' system property to 'true' to forcefully connect to the REST connector (configured on a node via 'org.apache.ignite.configuration.ConnectorConfiguration').`
72+
73+
To ensure backward compatibility, a system property has been added to provide the old behavior (note: it will be removed in version 2.18):
74+
75+
[tabs]
76+
--
77+
tab:Unix[]
78+
[source, shell]
79+
----
80+
export IGNITE_CONTROL_UTILITY_USE_CONNECTOR_CONNECTION=true;
81+
control.sh --state --host x.x.x.x --port 11212
82+
----
83+
tab:Windows[]
84+
[source, shell]
85+
----
86+
SET IGNITE_CONTROL_UTILITY_USE_CONNECTOR_CONNECTION=true
87+
control.bat --state --host x.x.x.x --port 11212
88+
----
89+
--
90+
91+
In some cases, the following actions may be required to migrate user scripts using the utility:
92+
93+
=== 1. A custom port is specified:
94+
95+
[tabs]
96+
--
97+
tab:Unix[]
98+
[source, shell]
99+
----
100+
control.sh --state --host x.x.x.x --port 11212
101+
----
102+
tab:Windows[]
103+
[source, shell]
104+
----
105+
control.bat --state --host x.x.x.x --port 11212
106+
----
107+
--
108+
109+
To migrate, specify the port for the thin client connector:
110+
111+
[tabs]
112+
--
113+
tab:Unix[]
114+
[source, shell]
115+
----
116+
control.sh --state --host x.x.x.x
117+
control.sh --state --host x.x.x.x --port 10801
118+
----
119+
tab:Windows[]
120+
[source, shell]
121+
----
122+
control.bat --state --host x.x.x.x
123+
control.bat --state --host x.x.x.x --port 10801
124+
----
125+
--
126+
127+
=== 2. A custom SSL factory for the binary REST connector is specified, different from the SSL factory for the thin client connector:
128+
129+
[tabs]
130+
--
131+
tab:Unix[]
132+
[source, shell]
133+
----
134+
control.sh --state --ssl-factory connector-ssl-factory.xml
135+
----
136+
tab:Windows[]
137+
[source, shell]
138+
----
139+
control.bat --state --ssl-factory connector-ssl-factory.xml
140+
----
141+
--
142+
143+
To migrate, specify the SSL factory for the thin client connector:
144+
145+
[tabs]
146+
--
147+
tab:Unix[]
148+
[source, shell]
149+
----
150+
control.sh --state --ssl-factory ignite-ssl-factory.xml
151+
control.sh --state --ssl-factory client-connector-ssl-factory.xml
152+
----
153+
tab:Windows[]
154+
[source, shell]
155+
----
156+
control.bat --state --ssl-factory ignite-ssl-factory.xml
157+
control.bat --state --ssl-factory client-connector-ssl-factory.xml
158+
----
159+
--
160+
161+
=== 3. The client connector is disabled.
162+
163+
Enable it in the configuration (`IgniteConfiguration#setClientConnectorConfiguration`).
66164

67165
== Activation, Deactivation and Topology Management
68166

0 commit comments

Comments
 (0)