Edit

Ignite Clients

Ignite 3 clients connect to the cluster via a standard socket connection. Unlike Ignite 2.x, there is no separate Thin and Thick clients in Ignite 3. All clients are 'thin'.

Clients do not become a part of the cluster topology, never hold any data, and are not used as a destination for compute calculations.

Client Connector Configuration

Client connection parameters are controlled by the client connector configuration. By default, Ignite accepts client connections on port 10800. You can change the configuration for the node by using the CLI tool at any time.

Here is how the client connector configuration looks like:

{
  "ignite" : {
    "clientConnector" : {
      "connectTimeout" : 5000,
      "idleTimeout" : 0,
      "listenAddresses" : "",
      "metricsEnabled" : false,
      "port" : 10800,
      "sendServerExceptionStackTraceToClient" : false,
      "ssl" : {
        "ciphers" : "",
        "clientAuth" : "none",
        "enabled" : false,
          "keyStore" : {
            "password" : "********",
            "path" : "",
            "type" : "PKCS12"
        },
        "trustStore" : {
          "password" : "********",
          "path" : "",
          "type" : "PKCS12"
        }
      }
    }
  }
}

The table below covers the configuration for client connector:

Property Default Description

connectTimeout

5000

Connection attempt timeout, in milliseconds.

idleTimeout

How long the client can be idle before the connection is dropped,in milliseconds. By default, there is no limit.

metricsEnabled

false

Defines if client metrics are collected.

port

10800

The port the client connector will be listening to.

sendServerExceptionStackTraceToClient

false

By default, only the exception message and code are sent back to the client.

Set this property to true to include the full stack trace, which will appear as part of the client-side exception.

Note	Not recommended for production: stack trace disclosure is a security weakness.

ssl.ciphers

The cipher used for SSL communication.

ssl.clientAuth

Type of client authentication used by clients. For more information, see SSL/TLS.

ssl.enabled

Defines if SSL is enabled.

ssl.keyStore.password

SSL keystore password.

ssl.keyStore.path

Path to the SSL keystore.

ssl.keyStore.type

PKCS12

The type of SSL keystore used.

ssl.trustStore.password

SSL keystore password.

ssl.trustStore.path

Path to the SSL keystore.

ssl.trustStore.type

PKCS12

The type of SSL keystore used.

Here is how you can change the parameters:

node config update clientConnector.port=10469

Limitations

There are limitations to user types that can be used for such a mapping. Some limitations are common, and others are platform-specific due to the programming language used.

Only flat field structure is supported, meaning no nesting user objects. This is because Ignite tables, and therefore tuples have flat structure themselves;
Fields should be mapped to Ignite types;
All fields in user type should either be mapped to Table column or explicitly excluded;
All columns from Table should be mapped to some field in the user type;
Java only: Users should implement Mapper classes for user types for more flexibility;

Partition Awareness

In Ignite 3, partition awareness is enabled automatically for all clients.

Data in the cluster is distributed between the nodes in a balanced manner for scalability and performance reasons. Each cluster node maintains a subset of the data, and the partition distribution map, which is used to determine the node that keeps the primary/backup copy of requested entries.

Partition awareness allows the client to send query requests directly to the node that owns the queried data.

Without partition awareness, an application that is connected to the cluster via a client would execute all queries and operations via a single server node that acts as a proxy for the incoming requests. These operations would then be re-routed to the node that stores the data that is being requested. This would result in a bottleneck that could prevent the application from scaling linearly.

Notice how queries must pass through the proxy server node, where they are routed to the correct node.

With partition awareness in place, the client can directly route queries and operations to the primary nodes that own the data required for the queries. This eliminates the bottleneck, allowing the application to scale more easily.

© 2025 The Apache Software Foundation.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.