Connect to a Distributed System Using Locators

SQLFire thin clients specify the client bind address and port of a locator in order to connect to a SQLFire cluster.

Connecting to a locator ensures that a client is load-balanced to an available SQLFire server in the distributed system. If the client's connection to a server is dropped (for example, if the server is shut down), then the client can retry connecting to the same locator to access another available server.

Note: Thin clients do not specify the peer discovery addresses or port as do SQLFire servers and peers.
For example, in an interactive sqlf session, use the connect client command and specify the client host and port number of a locator:
connect client 'locator1host:1527';

In a third-party JDBC tool, specify the host and port in the JDBC connection string:

jdbc:sqlfire://locator1host:1527

Locators balance client requests to all SQLFire servers available in a cluster, so multiple connection requests to the same locator may result in connections to different servers.