This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Ignite Persistent Store - under the hood

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Summary, limitations and performance

Persistence files

Ignite with enabled persistence uses following folder stucture

Image Added

Consistent ID may be configured using IgniteConfiguration or generated from local IPs set

There are following file types used for persisting data: Cache pages or page store, Checkpoint markers, and WAL segments

Image Modified

  • WAL segments - constant size file (WAL work directory 0...9.wal;, WAL archive 0.wal…)
  • CP markers (UUID-Begin.bin, UUID-End.bin)
  • Page store (Now implemented as uses file per partition: cache-(cache_name)\part1,2,3.bin, and index.bin)

Consistent state comes only from pair of WAL and page store.



DEFAULTfsync() on each commitAny crashes (OS and process crash)

write() on commit

Synchronisation is responsibility of OS

Kill process, but no OS fail

do nothing on commit

(records are accumulated in memory)

write() on timeout

kill -9 may cause loss of several latest updates