org.apache.ignite.client

## Interface ClientAddressFinder

- All Known Implementing Classes:
    ThinClientKubernetesAddressFinder

      public interface ClientAddressFinder

  This interface provides a list of addresses of Ignite server nodes within a cluster. Thin client uses the list to route user requests. There are cases when the list is not static, for example in cloud environment. In such cases addresses of nodes and/or number of server nodes can change. Implementation of this interface should handle these. Ignite waits for a topology change to trigger `getAddresses()`. There are two modes of how soon Ignite calls it, lazy and eager, depending on whether the partition awareness feature is enabled. If the feature is enabled then Ignite calls the method for every topology change. Otherwise Ignite uses previous addresses until a first failure. `ClientConfiguration.setPartitionAwarenessEnabled(boolean)` `ClientConfiguration.setAddressesFinder(ClientAddressFinder)`

- - ### Method Summary

    All Methods Instance Methods Abstract Methods
    Modifier and Type | Method and Description
    --- | ---
    `String[]` | `getAddresses()` Get addresses of Ignite server nodes within a cluster.

- - ### Method Detail

    - #### getAddresses

          String[] getAddresses()

      Get addresses of Ignite server nodes within a cluster. An address can be IPv4 address or hostname, with or without port. If port is not set then Ignite will generate multiple addresses for default port range. See `ClientConnectorConfiguration.DFLT_PORT`, `ClientConnectorConfiguration.DFLT_PORT_RANGE`.
      Returns:
        Addresses of Ignite server nodes within a cluster.

${current.year} Copyright © Apache Software Foundation
| Follow @ApacheIgnite
Ignite Database and Caching Platform | : ver. 2.15.0
Release Date | : April 25 2023