Saturday, December 10, 2016

Distributed in-memory Cache - Apache Ignite

Apache Ignite is highly performant because it has a deep history of distributed deployment with sql, transactional and locking support.  It was recently open sourced to Apache.

Mixed metal and VM's
[19:05:22] Ignite node started OK (id=7352a302)
[19:05:22] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=12.0GB]
[19:05:32] Topology snapshot [ver=2, servers=2, clients=0, CPUs=8, heap=24.0GB]
[19:05:42] Topology snapshot [ver=3, servers=3, clients=0, CPUs=12, heap=36.0GB]
[19:05:50] Topology snapshot [ver=4, servers=4, clients=0, CPUs=16, heap=48.0GB]
[19:05:57] Topology snapshot [ver=5, servers=5, clients=0, CPUs=24, heap=60.0GB]
[19:06:07] Topology snapshot [ver=6, servers=6, clients=0, CPUs=30, heap=68.0GB]

[19:06:16] Topology snapshot [ver=7, servers=7, clients=0, CPUs=36, heap=76.0GB]

Bare Metal NUCs

VMware RHEL 7.3 Virtual Machines (bridged mode) across two physical hosts

GridGain Enterprise Edition 7.5 corresponds to Apache Ignite 1.5 in February 2016

Release 1.8.0 8 Dec 2016

Amazon Image

  • Download Apache Ignite as ZIP archive from
  • Unzip ZIP archive into the installation folder in your system
  • Set IGNITE_HOME environment variable to point to the installation folder and make sure there is no trailing / in the path (this step is optional)

Maven/Gradle dependencies




Open ports on all machines
47100 = local
48100 = shared memory

   90  wget
   91  unzip 

export IGNITE_HOME=/root/ignite-180

 bin/ examples/config/example-ignite.xml

No comments:

Total Pageviews