Apache Ignite Documentation

GridGain Developer Hub - Apache Ignitetm

Welcome to the Apache Ignite developer hub run by GridGain. Here you'll find comprehensive guides and documentation to help you start working with Apache Ignite as quickly as possible, as well as support if you get stuck.


GridGain also provides Community Edition which is a distribution of Apache Ignite made available by GridGain. It is the fastest and easiest way to get started with Apache Ignite. The Community Edition is generally more stable than the Apache Ignite release available from the Apache Ignite website and may contain extra bug fixes and features that have not made it yet into the release on the Apache website.


Let's jump right in!


Documentation     Ask a Question     Download


Javadoc     Scaladoc     Examples

Ignite Life Cycle

Manage life cycle of your Ignite nodes.

Ignite is JVM-based. A single JVM represents one or more logical Ignite nodes (most of the time, however, a single JVM runs just one Ignite node). Throughout the Ignite documentation, we use the terms Ignite runtime and Ignite node almost interchangeably. For example, when we say that you can "run 5 nodes on this host" - in most cases it technically means that you can start 5 JVMs on this host each running a single Ignite node. Ignite also supports multiple Ignite nodes in a single JVM. In fact, that is exactly how most of the internal tests run for Ignite.


Ignite runtime == JVM process == Ignite node (in most cases)

Ignition Class

The Ignition class starts individual Ignite nodes in the network topology. Note that a physical server (like a computer on the network) can have multiple Ignite nodes running on it.

Here is how you can start a grid node locally with all the defaults:

Ignite ignite = Ignition.start();

You can also start an Ignite node by passing a configuration file:

Ignite ignite = Ignition.start("examples/config/example-cache.xml");

The path to the configuration file can be absolute or relative to either IGNITE_HOME (Ignite installation folder) or META-INF folder in your classpath.


Sometimes you need to perform certain actions before or after the Ignite node starts or stops. This can be done by implementing the LifecycleBean interface, and specifying the implementation bean in the lifecycleBeans property of IgniteConfiguration in the spring XML file:

<bean class="org.apache.ignite.IgniteConfiguration">
    <property name="lifecycleBeans">
            <bean class="com.mycompany.MyLifecycleBean"/>

LifeCycleBean can also be configured programmatically:

// Create new configuration.
IgniteConfiguration cfg = new IgniteConfiguration();
// Provide lifecycle bean to configuration.
cfg.setLifecycleBeans(new MyLifecycleBean());
// Start Ignite node with given configuration.
Ignite ignite = Ignition.start(cfg)

An implementation of LifecycleBean may look like the following:

public class MyLifecycleBean implements LifecycleBean {
    @Override public void onLifecycleEvent(LifecycleEventType evt) {
        if (evt == LifecycleEventType.BEFORE_NODE_START) {
            // Do something.

You can inject an Ignite instance and other useful resources into a LifecycleBean implementation. Please refer to the Resource Injection section for more information.

Lifecycle Event Types

The following lifecycle event types are supported:

Event Type



Invoked before Ignite node startup routine is initiated.


Invoked right after Ignite node has started.


Invoked right before Ignite stop routine is initiated.


Invoked right after Ignite node has stopped.

Updated about a year ago

Ignite Life Cycle

Manage life cycle of your Ignite nodes.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.