Installation on z/OS
The easiest way to install GridGain on z/OS is to follow the manual installation procedure.
Prerequisites
-
Java 8+, tested with IBM J9 VM.
Installation
-
Download the GridGain Enterprise z/OS Edition as a zip archive. Please ask your account executive or contact our sales for the link.
-
Unzip the zip archive into the installation folder in your system.
-
(Optional) Enable any of the modules you might want to use.
-
Now you can launch a node.
To verify that installation is successful, go to the distribution directory and run the following command:
gridgain-zos-enterprise-8.8.3/bin/ignite.sh -v config/default-config.xml
If the node starts successfully, you will see the following message in the console:
Configuring GridGain
-
Please refer to configuration pages to configure your GridGain nodes. The configuration file provided with GridGain distribution will start an in-memory node with large data region, which should form a single-node cluster after start-up. You may need to tune the size of default data region to adjust resource usage.
-
Most text files are provided in native
EBCDIC 1047
code page. However, some files are required to be inASCII
-derived encoding, notably, configuration XML files. If you need to view or edit any of those, consider tagging them usingchtag
command, using the following command as reference:chtag -t -R -c ISO8859-1 path/to/file.xml
You can also read such files with the
iconv -cf IBM-1047 -t ISO8859-1 path/to/file.xml
command.
Running GridGain
-
Set the
MEMLIMIT
parameter. The parameter defines the limit on memory for a single process. Set it to a value that is larger than the RAM memory required for your GridGain nodes, including Heap and Off-Heap data regions. -
We recommend to always specify
-Dfile.encoding=UTF-8
JVM argument. You do not need to specify it if you start GridGain by runningignite.sh
. However, if you start nodes from custom code, add it to the startup parameters of your application. -
If you are going to use the native persistence feature, set the
IGNITE_WAL_MMAP
system property (or environment variable) tofalse
, for example, by adding-DIGNITE_WAL_MMAP=false
JVM argument. You do not need to specify it if you start GridGain by runningignite.sh
. -
Configure static discovery instead of the default multicast option. Specify the
TcpDiscoverySpi.localAddress
property and theIgniteConfiguration.localHost
property with the preferred IP address for the current host. You do not need to specify it if you start GridGain by using providedconfig/default-config.xml
. -
If you are going to use log4j for logging, you will need to specify charset/encoding of file appenders as
IBM-1047
in Log2J/Log4J2 configuration. Please use providedconfig/ignite-log4j.xml
andconfig/ignite-log4j2.xml
as reference.
Performance recommendations
-
For nodes with a persistent storage, increase the
dataStorage.checkpointThreads
value. The default value is4
, but we recommend you set it to a value between16
and32
on z/OS nodes for best checkpointing speed. -
If your load profile includes intensive network usage, consider the following
TcpCommunicationSpi
parameters:socketWriteTimeout=5000
(ms),usePairedConnections=true
, pick theconnectionsPerNode
value from between2
and8
. -
Nodes may benefit from a larger striped pool size, increase it by setting
IgniteConfiguration.stripedPoolSize
to 32.
© 2021 GridGain Systems, Inc. All Rights Reserved. Privacy Policy | Legal Notices. GridGain® is a registered trademark of GridGain Systems, Inc.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.