Page History

...

Previously existed eviction mechanisms based on `EvictionPolicy` is now supported only for optional near and Java heap caching of the data stored in the off-heap page memory. To enable the eviction for the page memory, use `DataPageEvictionMode` enumeration. Refer to this documentation for more details: https://apacheignite.readme.io/docs/evictions

Cache and Memory Metrics 

The following methods were removed from `CacheMetrics` interface as part of a migration to the off-heap memory architecture: getOverflowSize, getOffHeapMaxSize, getSwapGets, getSwapPuts, getSwapRemovals, getSwapHits, getSwapMisses, getSwapEntriesCount, getSwapSize, getSwapHitPercentage, getSwapMissPercentage. 

To support the new memory architecture, `MemoryMetrics` interface was introduced in order to get insights on a state and behavior of the memory in runtime. Refer to this documentation if you plan to leverage from this interface: https://apacheignite.readme.io/docs/memory-metrics

Default Cache Name

`null` can no longer be used as a cache name. If a cache is started with an empty named then it will be named `default` and you can get it using either `Ignite.cache(null)` or `Ignite.cache("default")` calls.

Ignite Node Configuration

• IgniteConfiguration's `getGridName/setGridName` methods are deprecated and will be removed in later releases. Use IgniteConfiguration's `getIgniteInstanceName/setIgniteInstanceName` instead.
  
  

• Service Grid calls are processed in a separated Service Grid thread pool which size can be tweaked over `IgniteConfiguration.setServiceThreadPoolSize(...)` method. Before that, the public thread pool served that purpose.
  
  
• Apache Ignite data streamer's calls are going to and processed by a dedicated data streamer's thread pool which size can be tweaked over `IgniteConfiguration.setDataStreamerThreadPoolSize(...)` method. Before that, the public thread pool served that purpose.
  
  
• SQL queries are now processed and executed using Threads from Queries thread pool size that is configurable via `IgniteConfiguration.setQueryThreadPoolSize(...)` method. Before that, the system thread pool was used for that purpose.
  
  

...

• Confusing `TcpDiscoverySPI.getHeartbeatFrequency` parameter is no longer supported. The parameter used to define a frequency of cluster and cache metrics that are sent by cluster nodes from one to another. Now the frequency can be adjusted with `IgniteConfiguration.setMetricsUpdateFrequency(...)` method.
  
  
• `TcpDiscoveryS3IpFinder.setAwsCredentials(AWSCredentialsProvider)` renamed to `TcpDiscoveryS3IpFinder.setAwsCredentialsProvider(AWSCredentialsProvider)`.
  
  
• Apache Ignite client nodes' failure detection timeout is now set with `IgniteConfiguration.setClientFailureDetectionTimeout(...)` and equal to 30 seconds be default. `IgniteConfiguration.getFailureDetectionTimeout()`, that is equal to 7 seconds, was used as the timeout for both server and client nodes in prior versions.

Redis Integration

Default Redis cache name was changed from 'null' to 'redis_cache'.

Ignite.NET

• CompiledQuery class removed, CompiledQuery2 class renamed to CompiledQuery. If you have used CompiledQuery class, there is nothing to change. Existing code should compile. If you have used CompiledQuery2 class, rename usages to CompiledQuery.
  
  
• CacheEvent.LockId has been removed. It was always null previously.
  
  
• BinaryConfiguration properties renamed: DefaultNameMapper -> NameMapper, DefaultIdMapper -> IdMapper, DefaultKeepDeserialized -> KeepDeserialized
  
  
• ILifecycleBean renamed to ILifecycleHandler, IgniteConfiguration.LifecycleBeans -> IgniteConfiguration.LifecycleHandlers

...