Sign inSign up

gridgain/gridgain9

By gridgain

•Updated 15 days ago

GridGain is an in-memory computing platform based Apache Ignite™

Image
Data science
Databases & storage
1

10K+

gridgain/gridgain9 repository overview

⁠GridGain9 Docker Image

⁠About GridGain 9

GridGain 9 is a unified real-time data platform built on Apache Ignite™ that includes the Apache Ignite codebase, along with improvements and additional functionality developed by GridGain Systems to enhance Apache Ignite's performance and reliability.

⁠Running a Node

Use the' docker run' command to run GridGain in a Docker container.

sudo docker run -d gridgain/gridgain9

This command starts a single GridGain node.

⁠Starting CLI Tool

When the node starts, you need to initialize the cluster. We recommend using the GridGain Try Free⁠ link to download and install the GridGain CLI tool. Once you start the tool, you can start the cluster with the following command:

If needed, you can still run the CLI tool in Docker:

sudo docker run -it gridgain/gridgain9:9.0.0 cli

All the following instructions will use the CLI tool.

⁠Adding Nodes to NodeFinder

When the node is started, it checks the addresses specified in the network.nodeFinder.netClusterNodes configuration to find other nodes in the network. You need to provide the list of all node addresses that will form the cluster.

node config update network.nodeFinder.netClusterNodes=["localhost:3344", "otherHost:3344"]

You can check if the nodes have found each other by using the cluster topology physical command.

cluster topology physical

⁠Initializing a Cluster

From the CLI tool, initialize the cluster:

cluster init --name=sampleCluster --metastorage-group=defaultNode --config-files=license.conf

To get the licence file, use the Contact GridGain support⁠ link.

You can check if the nodes have found each other by using the cluster topology logical command.

cluster topology logical

⁠Managing Node Configuration

Node configuration is managed via the CLI tool, for example:

node config update network.shutdownTimeout=20000

After the node configuration is changed, restart the node.

⁠Managing Cluster Configuration

Cluster configuration is managed via the CLI tool, for example:

cluster config update metaStorage.idleSyncTimeInterval=600

The cluster configuration is automatically propagated to all nodes in the cluster.

⁠Extended Documentation

GridGain documentation⁠ has more information about running GridGain 9.

Tag summary

Content type

Image

Digest

sha256:877ac1a35…

Size

649.1 MB

Last updated

15 days ago

docker pull gridgain/gridgain9