Client connector configuration (ODBC, JDBC, Thin Client).
Defines custom data region configuration for Apache Ignite page memory (see DataStorageConfiguration).
For each configured data region Apache Ignite instantiates respective memory regions with different parameters like maximum size, eviction policy, swapping options, etc. An Apache Ignite cache can be mapped to a particular region using DataRegionName method.
Data storage configuration for Ignite page memory.
The page memory is a manageable off-heap based memory architecture that divides all expandable data regions into pages of fixed size. An individual page can store one or many cache key-value entries that allows reusing the memory in the most efficient way and avoid memory fragmentation issues.
By default, the page memory allocates a single expandable data region. All the caches that will be configured in an application will be mapped to this data region by default, thus, all the cache data will reside in that data region.
Custom thread pool configuration for compute tasks. See WithExecutor(String).
SQL connector configuration (for ODBC and JDBC).
Data storage configuration for system cache.
Server-side thin client specific configuration.
Defines async continuations behavior.
Defines checkpoint pages order on disk.
Memory page eviction mode. Only data pages, that store key-value entries, are eligible for eviction. The other types of pages, like index or system pages, are not evictable.
Disk page compression options.
Write Ahead Log mode.