THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!

Versions Compared

Old Version 10

changes.mady.by.user Nikolai Tikhonov

Saved on

compared with

New Version 11

changes.mady.by.user Ilya Kasnacheev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Replace WORK -> WORKING as per https://stackoverflow.com/questions/54859857/apache-ignite-yarn-deployment-hdfs-issue

...

All configuration is handled through environment variables or property file. Following configuration parameters can be optionally configured.

NameDescriptionDefaultExample

IGNITE_RUN_CPU_PER_NODE

The number of CPU Cores for each Apache Ignite node.

2

4

IGNITE_MEMORY_PER_NODE

The number of Megabytes of RAM for each Apache Ignite node.

2048

1024

IGNITE_NODE_COUNT

The number of nodes in the cluster.

3

10

IGNITE_VERSION

The version ignite which will be run on nodes.

latest

1.0.5

IGNITE_WORKWORKING_DIR

The directory which will be used for saving Apache Ignite distributives.

./ignite-release

/opt/ignite/

IGNITE_RELEASES_DIRThe hdfs directory which will be used for saving Apache Ignite distributives./ignite/releases//ignite-rel/ 

IGNITE_XML_CONFIG

The hdfs path to Apache Ignite config file.

N/A

/opt/ignite/ignite-config.xml

IGNITE_USERS_LIBS

The hdfs path to libs which will be added to classpath.

N/A

/opt/libs/

IGNITE_HOSTNAME_CONSTRAINTThe constraint on slave hosts.N/A192.168.0.[1-100]