You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the code above provides a failover mechanism in case of server node failures. Refer to the <<Handling Node Failures>> section for more information.
77
77
78
+
[[discovery]]
79
+
=== Automatic Server Node Discovery
80
+
81
+
Thin client can discover server nodes in the cluster automatically.
82
+
This behavior is enabled when `ClientConfiguration.clusterDiscoveryEnabled` is enabled (`true` by default).
83
+
84
+
Server discovery is an asynchronous process - it happens in the background.
85
+
Additionally, thin client receives topology updates only when it performs some operations (to minimize server load and network traffic from idle connections).
86
+
87
+
[WARNING]
88
+
====
89
+
[discrete]
90
+
Server discovery may not work when servers are behind a NAT server or a proxy.
91
+
Server nodes provide their addresses and ports to the client, but when the client is in a different subnet, those addresses won't work.
92
+
====
93
+
94
+
==== Host Names and TLS
95
+
96
+
By default, server nodes advertise their IP addresses during discovery.
97
+
If clients must connect using host names (for example, when TLS is enabled and certificates contain host names),
98
+
configure each server node to advertise its host name by setting `IgniteConfiguration#localHost` on the *server* side.
99
+
100
+
[source, java]
101
+
----
102
+
IgniteConfiguration cfg = new IgniteConfiguration()
0 commit comments