Apache Ignite 2.9.1 version released, minor version update

Apache Ignite release notes
===========================
Apache Ignite memory computing platform 2.9.1
---------- -------------------------------------------------

Ignite core:

  • Added support for graceful shutdown of ZookeeperDiscoverySpi;
  • Added a system view of binary metadata;
  • Added system view of metadata storage;
  • Added RebalancingPartitionsTotal indicator;
  • Improved concurrent behavior of checkpoints;
  • Fixed the issue that caused serious system errors when unregistering JMX Bean;
  • Fixed the issue that IgniteCache#isClosed() would return false even if the cache is closed;
  • Fixed the problem that expired cache items cannot be deleted immediately;
  • Fixed the problem that some indexes failed to rebuild when the index cache has different data types;
  • Fixed the view error of the local meta storage system when unmarshallable values ​​appear;
  • Fixed the deadlock problem between grid-timeout-worker and the open communication connection thread;
  • Fixed the deadlock problem in IgniteServiceProcessor;
  • Fixed the problem that scan query failed due to assertion error: Unexpected row key;
  • Fixed the archive problem when the server restarts after enabling the Wal compression setting;
  • Fixed the null pointer problem when initializing Cassandra storage with PRIMITIVE strategy;
  • Fixed the synchronization problem when different class loaders are used for the deployment of the same class;
  • Fixed the problem that the SQL cache may be abnormal when the client reconnects;
  • Fixed the problem of possible deadlock when deleting multiple caches;
  • Fixed the problem that IgniteServiceProcessor may have a null pointer when destroying a cache;
  • Fixed the problem related to the deserialization of the cache interceptor on the client node;
  • Fixed the problem that control.sh cannot be started if the JMX port is configured;
  • Fixed the problem that ZookeeperDiscoverySpiMBeanImpl#getCoordinator could not return a valid node as the coordinator;
  • Fixed several log issues;
  • Fixed the problem that the exchange process was considered blocked when waiting for a new task in the queue;
  • Fixed the problem that the output of topology snapshot log about coordinator changes is incorrect;
  • Fixed the problem of slow node initialization process;
  • Fixed the incorrect use of Class.isAssignableFrom in SystemViewLocal and SystemViewMBean;
  • Fixed the concurrency problem of several indicators;
  • Fixed the problem that the predicate (< and >) in the WHERE clause with composite primary key was not handled correctly;
  • Remove unnecessary dependencies in curator-client and improve ZookeeperDiscoverySpi;
  • Removed unnecessary error tracking in IgnitionEx;

Java thin client:

  • Fixed the issue that may cause partition differences in the ignite sys cache when the thin client connects/disconnects during the topology update;
  • Fixed the problem that the thin client silently closes the connection channel after inactivity;
  • Fixed the abnormal issue of protocol version not supported when getting cache configuration from Java thin client;

JDBC:

  • Fixed the problem that the thin mode driver reports incorrect attribute names;
  • Updated the JDBC metadata to match the actual function;

Ignite .NET:

  • Improved the slow serialization speed of enumeration;
  • Fixed the problem of deserialization when the IBinaryObject field is included in the IBinaryObject;
  • Fixed the problem that TransactionImpl's finalizer may cause the process to crash;
  • Fixed the problem that the child process becomes a zombie process when using direct IO persistently on Linux.

Ignite C++:

  • CMake build system adds support for Windows;
  • Fixed the problem that odbc-example loses value when running with an additional node.

Guess you like

Origin www.oschina.net/news/124976/ignite-2-9-1-released