Apache Ignite 2.9 Released: Cluster snapshots and tracing
As of October 23, 2020, Apache Ignite 2.9 is available. Like every other Ignite release, release 2.9 includes many changes. Let's take a look at the major features of release 2.9.
Ignite 2.9 provides the ability to create full cluster snapshots for deployments that use Ignite Persistence. Snapshots can be taken online, when the cluster is active and accessible to users. An Ignite snapshot includes a cluster-wide copy of all data records that exist at the moment the snapshot is started. All snapshots are consistent — in terms of concurrent, cluster-wide operations as well as in terms of ongoing changes in Ignite Persistence data, index, schema, binary metadata, marshaller, and other files on nodes. See Ignite documentation to learn about this feature.
The Ignite monitoring system continues to improve. In Ignite 2.9, a new tracing subsystem became available. Tracing provides information that is useful for debugging — that helps with both regular, daily, basic system monitoring and with incident analysis. You can collect distributed traces of tasks that are executed in your cluster and use this information to diagnose latency problems. In the 2.9 release, the following Ignite components are instrumented for tracing:
See the documentation for more information.
In addition to snapshots and tracing, Ignite 2.9 provides the following new features:
- Cluster discovery, cluster API, compute API, and service invocation support for thin clients (Java and .Net)
- Cluster-wide, read-only mode
- Ability to run user-defined code inside the Ignite sandbox
- Transparent data encryption: master key rotation
- Management tools to cancel user tasks and queries
- Platform cache (.Net)
See the release notes to learn about all of the new features.
Ignite contributors and committers
Posted at 11:10PM Nov 05, 2020 by Denis Magda in General | |