THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
If Ignite Persistence is used then after a restart Ignite will load the tree's root node (metadata page) and be able to iterate over the tree layers preloading each new missing page in memory from disk on demand. Also, the tree pages can be merged into one if less of 50% of space within page is used by payload data.
Missing picture to be added
B+Tree are used for SQL indexes: tree maps field value to reference to entry value.
...
This section describes possible pages and entries operations related to rotation with disk or completely removal data from grid.
| Term | Activated | Comments | Configuration | Level of operation | In memory only mode | Persistency mode |
|---|---|---|---|---|---|---|
Expiration (aka TTL) | Time | Sets expire time of entry after entry creation/access/update | ExpiryPolicy (Factory) | Entry |
|
|
Eviction | Region is full | Completely removes entry from grid. Reasonable with 3rd party persistence | PageEvictionMode | Entry (+ page is used to find more entries to remove) |
| N/A |
On Heap eviction | Depends on policy | Near caches and On-Heap caches (1.x) | EvictionPolicy | Entry |
| |
Page replacement | Region is full | Ignite operates | Not configurable by user | Page | N/A |
|
Page replacement (rotation with disk)
...
All data may be separated by user to following classes: archive data and operational data:
|
|
|---|
User now can specify how much memory it is possible to allocate for cache group.
...
Overview
Content Tools
Apps