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

Checkpointing

Overview

Since the WAL file constantly grows, it takes a significant amount of time to recover the cluster by going over the file from head to tail. To mitigate this, Ignite introduces a checkpointing process.

Checkpointing is the process of copying dirty pages from RAM to partition files on disk. A dirty page is a page that was updated in RAM but was not written to a respective partition file (an update was just appended to the WAL).

This process helps to utilize disk space frugally by keeping pages in the most up-to-date state on disk and allowing the removal of outdated WAL segments (files) from the WAL archive.

How it Works

Let's review an execution flow of a simple update operation, as shown below:

WAL and Checkpointing

WAL and Checkpointing

  1. Once a cluster node receives an update request, it will look up the data page in RAM where the value is to be inserted or updated. The page will be updated and marked as dirty.
  2. The update is appended to the tail of the WAL.
  3. The node sends an acknowledgment to the update initiator confirming the success of the operation.
  4. Checkpointing is triggered periodically depending on the frequency set in your configuration or other parameters. The dirty pages are copied from RAM to disk and passed on to specific partition files.

Checkpointing Tuning

Refer to the pages writes throttling and checkpointing buffers sections for guidance.

Checkpointing


Suggested Edits are limited on API Reference Pages

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