GridGain Developers Hub

Frequently Asked Questions

This section contains answers to common questions and recommendations for common issues.

Control Center lost connection to my cluster after restart

The most common case for this is the cluster ID change. It can happen during the restart of an in-memory cluster, or if persistent data storage was lost for a persistent cluster.

If this happened, you can reattach the cluster and continue monitoring it. However, previously collected data and configuration settings will be lost. To avoid losing cluster information, configure a persistent cluster ID on your GridGain cluster.

Preserving Cluster ID

Without a global team:

For this example, we will assume that Control Center is running on

When starting the cluster, you need to prepare secret, cluster id and cluster tag:

  • Start your cluster and activate.

  • Run the following commands in this order:

    control.bat --property set --name control-center-agent-cluster-secret --val 88f5ea3c-9e50-11ec-b909-0242ac120002 --yes
    control.bat --change-id 11111111-1111-1111-1111-111111111111 --yes
    control.bat --change-tag prod_cluster --yes
    management.bat --uri
  • Use the token command once and attach your cluster:

    management.bat --token

If you lose persistence, next time just run all commands except --token again.

With the global team

First, you need to configure the link: [global team] in Control Center with the account.globalTeam.enabled and account.globalTeam.attachCluster properties. With it configured, you no longer need to create a token.

  • Start your cluster and activate it.

  • Run the following commands in the order you see: --property set --name control-center-agent-cluster-secret --val 88f5ea3c-9e50-11ec-b909-0242ac120002 --yes --change-id 11111111-1111-1111-1111-111111111111 --yes --change-tag prod_cluster --yes

How can I automate connection of clusters to Control Center?

For persistent clusters, you only need to enable the Control Center Global Team by enabling the account.globalTeam.enabled and account.globalTeam.attachCluster properties.

For in-memory clusters, consider adding a small persistent data region. It can be used to store system information, while your caches are still in-memory. If this is not possible, set cluster secret, ID, and other properties after each cluster restart by using the control script. To do this, run the following commands when starting the cluster: --property --set --name secret --val UUID --change-id UUID

How do I contact support?

To contact support from the UI, use the Contact Us button in top-right of the screen. You can also send an e-mail to Our team is constantly monitoring feedback.

Contact Us