GridGain Developers Hub

Connecting to Demo Cluster

To make it simpler to see what Control Center offers you, GridGain provides a preconfigured demo that you can use to see how real applications look like.

If you already have a GridGain cluster, you can skip this step and connect to your own cluster as described in the next step.


You will need some tools preconfigured to run the demo cluster:

  • Docker 19 or later, or Docker Desktop Community 2.3 or later;

  • Docker Compose 1.25.5 or later;

  • Apache Maven 3.3 or later.

Download the Demo project

The demo project has a simple preconfigured GridGain cluster that you can run with Docker and a simple application that simulates load on it. Download and unzip the source repository or use Git to clone the repository:

git clone

The project is configured to run with GridGain Nebula. To make it compatible with locally run Control Center, add the following to docker/ignite-cluster.yaml file

    - "host.docker.internal:host-gateway"

This allows GridGain nodes to find the local copy of Control Center. If your copy of Control Center runs in Docker or on a different machine, this step is not necessary.

Start Demo GridGain Cluster

Open the demo folder and start a two-node GridGain cluster, with each node running as a separate container:

docker-compose -f docker/ignite-cluster.yaml up -d --scale ignite-server-node=2

The cluster nodes will store data in ignite-streaming-monitoring-demo\work\db folder. By default, 150MB is allocated per node.

Connect to Control Center

By default, GridGain nodes connect to GridGain Nebula. To work with a local copy of Control Center, change the address for the cluster to connect to:

  1. Connect to the container of the first cluster node:

    docker exec -it docker-ignite-server-node-1 bash
  2. Go into the /opt/gridgain/bin/ folder of the container:

    cd /opt/gridgain/bin/
  3. Instruct the cluster to connect to the local Control Center container:

    ./ --uri http://localhost:3000
  4. Generate and a new one-time token to register the cluster with the tool:

    ./ --token

    Make sure to save the token you generated to use on the next step of the tutorial.

  5. Quit the node’s container:


Now, the cluster is configured to work with the local installation of Control Center. You can go to Control Center and connect to it:

  • In Control Center, click Attach Cluster.

  • In the Attach Cluster wizard, make sure you have GridGain selected and enter the connection token. Then, click Continue.

  • The following step of the wizard will show the cluster being successfully attached.

    Now Control Center is connected to the nodes in Docker. You can see the dashboard with metrics.

  • New GridGain clusters start inactive. Activate your cluster from the Dashboard to enable the subsequent steps.

Launch Market Orders Application

Now that the cluster is running and connected, launch the application to simulate load for it. You need Internet connection, as the application will connect to PubNub Market Order data stream.

  1. Create an executable file:

    mvn clean package
  2. Dockerize the application:

    docker build -f docker/StreamingAppDockerfile -t ignite-streaming-app .
  3. Deploy the application in Docker:

    docker-compose -f docker/ignite-streaming-app.yaml up -d

Check Messages

Your cluster should be receiving messages. You can check what those messages are from SQL screen, for example:

SELECT * FROM Trade ORDER BY order_date DESC LIMIT 10;

Next Steps

Now you have a working cluster with some simulated load. Feel free to explore and try various Control Center features. GridGain nodes you launched are running GridGain Community, but you can do the same steps by starting Apache Ignite or GridGain Ultimate nodes.

To explore more feature of Control Center you can: