Registers a distributed object listener to cluster.
registration id of the listener.
distributed object listener function. This will be called with DistributedObjectEvent.
Returns the CP subsystem that offers a set of in-memory linearizable data structures.
Returns configuration that this instance started with. The returned object should not be modified.
Returns all DistributedObjects, that is all maps, queues, topics, locks etc.
The results are returned on a best-effort basis. The result might miss just-created objects and contain just-deleted objects. An existing object can also be missing from the list occasionally. One cluster member is queried to obtain the list.
the collection of all instances in the cluster
Returns the distributed Flake ID Generator instance with given name.
Returns the lifecycle service for this client.
Gathers information of this local client.
Returns the partition service of this client.
Returns the distributed Replicated Map instance with given name.
Returns a distributed Ringbuffer instance with the given name.
Returns a service to execute distributed SQL queries.
SQL service
see SqlService
Static newCreates a new client object and automatically connects to cluster.
InvalidConfigurationError before returning if config is not a valid configuration object.
a new client instance
Optional config: ClientConfigClient config. Default client config is used when this parameter is absent.
Static newCreates a client with cluster switch capability. Client will try to connect to alternative clusters according to failover configuration when it disconnects from a cluster.
a new client instance
InvalidConfigurationError before returning if the provided failover configuration is not valid
Optional failoverConfig: ClientFailoverConfigConfiguration object describing the failover client configs and try count
Generated using TypeDoc
Hazelcast client instance. When you want to use Hazelcast's distributed data structures, you must first create a client instance. Multiple instances can be created on a single Node.js process.
Client instances should be shut down explicitly.