October 20th, Q&A session: Get you issues solved and questions answered!

GitHub logo
Edit

Clustering

Overview

In this chapter, we discuss different ways nodes can discover each other to form a cluster.

On start-up, a node is assigned either one of the two roles: server node or client node. Server nodes are the workhorses of the cluster; they cache data, execute compute tasks, etc. Client nodes join the topology as regular nodes but they do not store data. Client nodes are used to stream data into the cluster and execute user queries.

To form a cluster, each node must be able to connect to all other nodes. To ensure that, a proper discovery mechanism must be configured.

Note
In addition to client nodes, you can use Thin Clients to define and manipulate data in the cluster. Learn more about the thin clients in the Thin Clients section.
Ignite Cluster

Discovery Mechanisms

Nodes can automatically discover each other and form a cluster. This allows you to scale out when needed without having to restart the whole cluster. Developers can also leverage Ignite’s hybrid cloud support that allows establishing connection between private and public clouds such as Amazon Web Services, providing them with the best of both worlds.

Ignite provides two implementations of the discovery mechanism intended for different usage scenarios:

  • TCP/IP Discovery is designed and optimized for 100s of nodes.

  • ZooKeeper Discovery that allows scaling Ignite clusters to 100s and 1000s of nodes preserving linear scalability and performance.