Installing and Starting GridGain

Set the JAVA_HOME environment variable or Windows PATH to point to the Java installation directory.

GridGain uses proprietary SDK APIs that are not available by default. You need to pass specific flags to JVM to make these APIs available. If you use the start-up script ignite.sh (or ignite.bat for Windows), you do not need to do anything because these flags are already set up in the script. Otherwise, provide the following parameters to the JVM of your application:

--add-exports=java.base/jdk.internal.misc=ALL-UNNAMED
# Used to get access to java UNSAFE (access to offheap memory).

--illegal-access=permit
# Allows access to private fields without accessors, used for dependency injection in user classes (for example, @IgniteInstanceResource annotation).

--add-exports=java.base/sun.nio.ch=ALL-UNNAMED
# Used for java.nio Selector optimization.

--add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED
# Used to enable JMX monitoring capability.

--add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
# Used to allow jvisualvm to connect to Ignite process.

--add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED
# Used for fast object construction during marshalling/unmarshalling.

TLSv1.3, which is available in Java 11, is not supported at the moment. Consider adding -Djdk.tls.client.protocols=TLSv1.2 if SSL between nodes is used.

Download the GridGain binary as a zip archive.

Unzip the zip archive into the installation folder in your system.

Move the ignite-rest-http folder from {gridgain}/libs/optional to {gridgain}/libs to enable the Ignite REST library for the cluster. The library is used by GridGain Web Console for cluster management and monitoring needs.

(Optional) Enable required modules.

(Optional) Set the IGNITE_HOME environment variable or Windows PATH to point to the installation folder and make sure there is no trailing / (or \ for Windows) in the path.