Actively publish entryprocessor to all servers

RELEASE_NOTES.txt

@@ -1,6 +1,120 @@
 Apache Ignite Release Notes
 ===========================
 
+Apache Ignite In-Memory Distributed Database 2.14.0
+-----------------------------------------------------------
+
+(!) WARNINGS:
+* Removed LOCAL caches support.
+* Removed scalar module.
+
+Ignite:
+* Added CDC binary meta change events.
+* Added a control.sh command that schedules index rebuild via the maintenance mode.
+* Added a pluggable affinity mapping function for the partition awareness usage.
+* Added a snapshot creation operation metrics.
+* Added a snapshot status command to control.sh and JMX.
+* Added a user info to the sql queries view.
+* Added an opportunity to specify a single partition for IndexQuery.
+* Added cache change events for CDCConsumer.
+* Added cache metrics command for Control Script.
+* Added support of optional beans for SpringResource annotation injection.
+* Added system view and histogram to show the distribution of hot and cold pages in the page memory.
+* Added the ability to define a custom path for the snapshot operation.
+* Added the ability to intercept calls to service methods.
+* Fixed 'Integer value is out of bounds' issue when the dataregion maxSize is large enough.
+* Fixed 'Invalid cross-device link error' when extending WAL segments size.
+* Fixed ClassCastException that appears during deployment manager stop in Java versions 11.0.16+ and 17.0.4+.
+* Fixed an issue that caused inconsistent keys after deletion during rebalance.
+* Fixed an issue that could lead to a block of the management pool in case of using clearSync.
+* Fixed an issue that could lead to unexpected partition map exchange on client nodes.
+* Fixed an issue where the snapshot error was not propagated to the initiating node.
+* Fixed an issue with potential node failure during the cancellation of computing jobs with cache operations.
+* Fixed applying expiration to CDC-replicated cache entries.
+* Fixed asynchronous operation permits overflow for explicit transaction with single write entry.
+* Fixed durable background task start on BLT node joined to the active cluster.
+* Fixed idle_verify command of control.sh utility.
+* Fixed incorrect node hostname resolution despite IP is configured with IGNITE_LOCAL_HOST.
+* Fixed incorrect params of GridCacheManager#stop method.
+* Fixed node resolving stale addresses from previously restarted and killed nodes.
+* Fixed nofication for node start event.
+* Fixed partition update counter tracking after the node restart.
+* Fixed potential deadlock in transactions recovery on node failure.
+* Fixed propagation of a service call exception stacktrace to the client side.
+* Fixed race condition in GridNioServer.
+* Fixed server-side message parsing for big messages from thin clients.
+* Fixed tasks for sending snapshot files.
+* Fixed the "io.datastorage.StorageSize" metrics in case of multiple persistence data regions.
+* Fixed the move of remote partition files during snapshot restore operations.
+* Fixed the run of ignitevisorcmd in JDK 17 environment.
+* Fixed writing of an empty binary object.
+* Fixed wrong checkpoint locks count calculation after lock timeout (wrong calculation leads to node failure in some cases).
+* Improved REST commands: skip authorization for  'Probe' and 'Version' commands.
+* Improved `--consistency repair` command of the control.sh utility; Read Repair now supports arrays and collections as values.
+* Improved `--consistency repair` command of the control.sh utility; Read Repair now supports binary keys.
+* Improved `--consistency repair` command of the control.sh utility; atomic caches can now be repaired by Read Repair.
+* Improved behavior of the speed-based throttling when a dirty-page ratio is low.
+* Improved consistency check, it now supports cacheGroup as a param as well.
+* Improved consistency check, it's now able to fix counters.
+* Improved index-reader.sh utility: add free size calculation.
+* Improved index-reader.sh utility: analyze and output information about the actual usage of inline space in the index.
+* Improved index-reader.sh utility: exclude repeated stack traces.
+* Improved inline size adjustment for fixed size index items.
+* Improved logging levels for situations when dealing with a client node.
+* Improved registered service name lookup performance and reduced service shutdown time.
+* Improved service name lookup performance and reduced service startup time.
+* Improved speed of the index-reader.sh utility.
+* Moved ignite-cloud IP Finder to the Ignite Extensions project.
+* Moved ignite-mesos to the Ignite Extensions project.
+* Moved ignite-spark modules to the Ignite Extensions project.
+* Moved ignite-yarn to the Ignite Extensions project.
+* Moved inigte-aop module to the Ignite Extensions project.
+* Removed deprecated log4j 1.x module.
+* Update Tomcat Servlet API dependency version to 9.0.63.
+* Update jsonpath dependency to 2.7.0.
+* Updated Jackson Databind dependency to 2.12.7 (CVE-2020-36518).
+* Updated Jetty dependency to 9.4.43.
+* Updated Lucene library version to 8.11.2.
+* Updated Spring dependency to 5.2.22.
+* Updated the MySql connector dependency version (fixes CVE-2021-2471, CVE-2022-21363).
+
+Java thin client:
+* Added AtomicLong.
+* Added IgniteSet.
+* Added automatic binary configuration. Name mapper and compact footer settings will be set according to cluster configuration.
+* Added partition awareness to AtomicLong - send network requests directly to the primary node for the given instance.
+* Added support of IndexQuery feature in Java thin client.
+* Fixed an issue that caused addresses not to be reloaded from ClientAddressFinder on connection loss.
+* Fixed hang on client startup when deprecated TLS version is used.
+* Fixed race condition and potential hang on client close.
+
+JDBC:
+* Fixed handling of BinaryObjectException on response to deserialization at the thin JDBC client
+* Fixed parsing quoted delimiters in CSV fields content for SQL command COPY.
+
+.Net thin client:
+* Added AtomicLong.
+
+.Net:
+* Fixed ServiceCallContext access from async methods.
+* Fixed StringComparer serialization.
+* Fixed net461 release binaries.
+* Improved Java detection on Linux.
+
+C++ thin client:
+* Added partition property to SqlFieldsQuery for C++ thin client.
+* Added support ScanQuery for C++ thin client.
+* Added user thread pool size to public configuration of the C++ thin client.
+
+SQL:
+* Added segmented indexes support for Calcite engine.
+* Added support for IN criterion for IndexQuery: IndexQuery.setCriteria(in("A", Arrays.asList(1, 2 ,3))).
+* Calcite-based SQL engine is now independent of H2-based SQL engine and doesn't require 'ignite-indexing' module and H2 to be in classpath anymore.
+* Fixed incorrect query result if a subquery with a filter was used on the left shoulder of a LEFT JOIN.
+* Fixed indexes registration after add/drop column for Calcite engine.
+* Fixed insertion of values with java LocalDate, LocalTime  and LocalDateTime types via SQL.
+* Improved SQL calcite: use index count scan for COUNT(*).
+
 Apache Ignite In-Memory Distributed Database 2.13.0
 -----------------------------------------------------------
 

bin/ignitevisorcmd.bat

@@ -131,7 +131,7 @@ if %ERRORLEVEL% neq 0 (
 ::
 :: ADD YOUR/CHANGE ADDITIONAL OPTIONS HERE
 ::
-if "%JVM_OPTS_VISOR%" == "" set JVM_OPTS_VISOR=-Xms1g -Xmx1g -XX:MaxPermSize=128M
+if "%JVM_OPTS_VISOR%" == "" set JVM_OPTS_VISOR=-Xms1g -Xmx1g
 
 ::
 :: Uncomment to set preference to IPv4 stack.

bin/ignitevisorcmd.sh

@@ -71,7 +71,7 @@ CP="${IGNITE_HOME}/bin/include/visor-common/*${SEP}${IGNITE_HOME}/bin/include/vi
 #
 # ADD YOUR/CHANGE ADDITIONAL OPTIONS HERE
 #
-JVM_OPTS="-Xms1g -Xmx1g -XX:MaxPermSize=128M -server ${JVM_OPTS}"
+JVM_OPTS="-Xms1g -Xmx1g -server ${JVM_OPTS}"
 
 # Mac OS specific support to display correct name in the dock.
 osname=`uname`

deliveries/docker/apache-ignite/x86_64/Dockerfile

@@ -15,8 +15,9 @@
 # limitations under the License.
 #
 
-# Start from Java 8 based on Alpine Linux image (~5Mb)
-FROM openjdk:8-jre-alpine
+# Start from Java 8 based on Alpine Linux image
+ARG JDK_VERSION=8
+FROM eclipse-temurin:${JDK_VERSION}-jre-alpine
 
 # Settings
 ENV IGNITE_HOME /opt/ignite/apache-ignite
@@ -46,3 +47,4 @@ CMD $IGNITE_HOME/run.sh
 
 # Container port exposure
 EXPOSE 11211 47100 47500 49112 10800 8080
+

docs/_data/toc.yaml

@@ -182,7 +182,7 @@
     - title: Using Cache Queries
       url: key-value-api/using-cache-queries
     - title: Read Repair
-      url: read-repair
+      url: key-value-api/read-repair
 - title: Performing Transactions
   url: key-value-api/transactions
 - title: Working with SQL

docs/_docs/SQL/sql-calcite.adoc

@@ -26,8 +26,6 @@ CAUTION: The Calcite-based query engine is currently in beta status.
 
 To use a Calcite-based engine, please make sure that the Calcite module libraries are in a classpath.
 
-CAUTION: Currently, a part of the `ignite-indexing` module functionality is reused, this means the `ignite-indexing` module also has to be present at classpath.
-
 === Standalone Mode
 
 When starting a standalone node, move `optional/ignite-calcite` folder to the `libs` folder before running `ignite.{sh|bat}` script. In this case, the content of the module folder is added to the classpath.

docs/_docs/clustering/connect-client-nodes.adoc

@@ -76,7 +76,7 @@ There are two discovery events that are triggered on the client node when it is
 * `EVT_CLIENT_NODE_RECONNECTED`
 
 You can listen to these events and execute custom actions in response.
-Refer to the link:events/listening-to-events[Listening to events] section for a code example.
+Please, refer to the link:events/listening-to-events[Listening to events] section for a code example.
 
 == Managing Slow Client Nodes
 

docs/_docs/code-snippets/java/pom.xml

@@ -24,7 +24,7 @@
     <version>1.0.0-SNAPSHOT</version>
     <properties>
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-        <ignite.version>2.13.0-SNAPSHOT</ignite.version>
+        <ignite.version>2.14.0</ignite.version>
     </properties>
     <dependencies>
         <dependency>

docs/_docs/code-snippets/java/src/main/java/org/apache/ignite/snippets/BasicCacheOperations.java

@@ -129,9 +129,10 @@ void readRepair() {
 
         try (Ignite ignite = Ignition.start()) {
             //tag::read-repair[]
-            IgniteCache<Object, Object> cache = ignite.cache("my_cache").withReadRepair();
+            IgniteCache<Object, Object> cache =
+                ignite.cache("my_cache").withReadRepair(ReadRepairStrategy.CHECK_ONLY);
 
-            Object value = cache.get(10);
+            Object value = cache.get(42);
             //end::read-repair[]
         }
 

docs/_docs/code-snippets/java/src/main/java/org/apache/ignite/snippets/ExternalStorage.java

@@ -73,8 +73,9 @@ public static void cacheJdbcPojoStoreExample() {
 
         personType.setKeyFields(new JdbcTypeField(java.sql.Types.INTEGER, "id", Integer.class, "id"));
 
-        personType.setValueFields(new JdbcTypeField(java.sql.Types.INTEGER, "id", Integer.class, "id"));
-        personType.setValueFields(new JdbcTypeField(java.sql.Types.VARCHAR, "name", String.class, "name"));
+        personType.setValueFields(
+            new JdbcTypeField(java.sql.Types.INTEGER, "id", Integer.class, "id"),
+            new JdbcTypeField(java.sql.Types.VARCHAR, "name", String.class, "name"));
 
         factory.setTypes(personType);
 

docs/_docs/code-snippets/k8s/stateful/node-configuration.xml

@@ -47,8 +47,8 @@
                     <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder">
                         <constructor-arg>
                             <bean class="org.apache.ignite.kubernetes.configuration.KubernetesConnectionConfiguration">
-                                <property name="namespace" value="default" />
-                                <property name="serviceName" value="ignite" />
+                                <property name="namespace" value="ignite" />
+                                <property name="serviceName" value="ignite-service" />
                             </bean>
                         </constructor-arg>
                     </bean>

docs/_docs/code-snippets/k8s/stateless/node-configuration.xml

@@ -31,8 +31,8 @@
                     <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder">
                         <constructor-arg>
                             <bean class="org.apache.ignite.kubernetes.configuration.KubernetesConnectionConfiguration">
-                                <property name="namespace" value="default" />
-                                <property name="serviceName" value="ignite" />
+                                <property name="namespace" value="ignite" />
+                                <property name="serviceName" value="ignite-service" />
                             </bean>
                         </constructor-arg>
                     </bean>

docs/_docs/extensions-and-integrations/change-data-capture-extensions.adoc

@@ -148,9 +148,11 @@ NOTE: Please, enable `ignite-cdc-ext` to be able to run `kafka-to-ignite.sh`.
 ==== Configuration
 
 Application configuration should be done using POJO classes or Spring xml file like regular Ignite node configuration.
-Kafka to ignite configuration file should contain the following beans that will be loaded during startup:
+Kafka to Ignite configuration file should contain the following beans that will be loaded during startup:
 
-. `IgniteConfiguration` bean: Configuration of the client node that will connect to the destination cluster.
+. One of the configuration beans to define a client type that will connect to the destination cluster:
+- `IgniteConfiguration` bean: Configuration of a client node.
+- `ClientConfiguration` bean: Configuration of a link:thin-clients/java-thin-client[Java Thin Client].
 . `java.util.Properties` bean with the name `kafkaProperties`: Single Kafka consumer configuration.
 . `org.apache.ignite.cdc.kafka.KafkaToIgniteCdcStreamerConfiguration` bean: Options specific to `kafka-to-ignite.sh` application.
 

docs/_docs/extensions-and-integrations/performance-statistics.adoc

@@ -52,6 +52,24 @@ For more details run the help command:
 performance-statistics-tool/build-report.sh --help
 ----
 
+=== Performance Statistics Report Example
+
+:perf_stat_url: images/integrations/performance-statistics
+
+[tabs]
+--
+tab:Cache operations[]
+image:{perf_stat_url}/perf_stat_2.jpg[Cache operations report]
+tab:Transactions[]
+image:{perf_stat_url}/perf_stat_3.jpg[Transactions report]
+tab:Queries[]
+image:{perf_stat_url}/perf_stat_4.jpg[Queries report]
+tab:Compute[]
+image:{perf_stat_url}/perf_stat_5.jpg[Compute report]
+tab:Cluster info[]
+image:{perf_stat_url}/perf_stat_1.jpg[Cluster info report]
+--
+
 == Print Statistics
 
 Ignite provides a tool to print statistics to a console or to a file in JSON format.

docs/_docs/key-value-api/read-repair.adoc

@@ -0,0 +1,99 @@
+// Licensed to the Apache Software Foundation (ASF) under one or more
+// contributor license agreements.  See the NOTICE file distributed with
+// this work for additional information regarding copyright ownership.
+// The ASF licenses this file to You under the Apache License, Version 2.0
+// (the "License"); you may not use this file except in compliance with
+// the License.  You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+= Read Repair
+
+WARNING: Experimental API
+
+[WARNING]
+====
+[discrete]
+=== Limitations
+A consistency check is incompatible with the following cache configurations:
+
+* Caches without backups.
+* Near caches.
+* Caches that use "read-through" mode.
+====
+
+
+`Read Repair` refers to a technique of repairing inconsistencies between primary and backup copies of data during normal read operations. When a specific key (or keys) is read by a user operation, Ignite checks the values for the given key in all backup copies.
+
+The `Read Repair` mode is designed to maintain consistency. However, read operations become {tilde}2 times more costly because backup copies are checked in addition to the primary copy. It is generally not advisable to use this mode all the time, but rather on a once-in-a-while basis.
+
+To enable the `Read Repair` mode, it is necessary to obtain an instance of the cache that enables Read Repair reads as follows:
+
+[source, java]
+----
+include::{javaCodeDir}/BasicCacheOperations.java[tags=read-repair, indent=0]
+----
+
+== Strategies
+In case consistency violations were found, the values across the topology will be replaced by repaired values according to the chosen strategy:
+
+[cols="1,4",opts="header"]
+|===
+| Strategy | Description
+| `LWW` a| Last write (the newest entry) wins.
+
+May cause IgniteException when the fix is impossible (unable to detect the newest entry)::
+* Null(s) found as well as non-null values for the same key. Null (missed entry) has no version, so, it can not be compared with the versioned entry.
+* Entries with the same version have different values.
+| `PRIMARY` | Value from the primary node wins.
+| `RELATIVE_MAJORITY` a| The relative majority, any value found more times than any other wins.
+Works for an even number of copies (which is typical of Ignite) instead of an absolute majority.
+
+May cause IgniteException when it is unable to detect values found more times than any other.
+
+For example, when 5 copies (4 backups) are given::
+* and value `A` found twice, but `X`, `Y` and `Z` only once, `A` wins,
+* but, when `A` is found twice, as well as `B`, and `X` only once, the strategy is unable to determine the winner.
+
+When 4 copies (3 backups) are given, any value found two or more times, when others are found only once, is the winner.
+| `REMOVE` | Inconsistent entries will be removed.
+| `CHECK_ONLY` | Only check will be performed.
+|===
+
+== Events
+link:https://ignite.apache.org/releases/{version}/javadoc/org/apache/ignite/events/EventType.html#EVT_CONSISTENCY_VIOLATION[Сonsistency Violation Event] will be recorded for each violation in case it's configured as recordable. You may listen to this event to get notified about inconsistency issues.
+
+Please, refer to the link:events/listening-to-events[Working with Events] section for the information on how to listen to events.
+
+== Transactional Caches
+Values will be repaired::
+* automatically for transactions that have `TransactionConcurrency.OPTIMISTIC` concurrency mode or `TransactionIsolation.READ_COMMITTED` isolation level,
+
+* at commit() phase for transactions that have `TransactionConcurrency.PESSIMISTIC` concurrency mode and isolation level other than `TransactionIsolation.READ_COMMITTED`
+
+[WARNING]
+====
+[discrete]
+=== Limitations
+This proxy usage does not guarantee "all copies check" in case the value have been already cached inside the transaction.
+
+In case you don't use a `READ_COMMITTED` isolation mode and already have a cached value, for example have already read the value or performed a write, you'll just get the cached value.
+====
+
+== Atomic Caches
+Values will be repaired automatically.
+
+[WARNING]
+====
+[discrete]
+=== Limitations
+Due to the nature of an atomic cache, false-positive results can be observed. For example, an attempt to check consistency under cache's loading may lead to a consistency violation exception.
+
+By default, the implementation tries to check the given key three times. The number of attempts can be changed using `IgniteSystemProperties.IGNITE_NEAR_GET_MAX_REMAPS` property.
+====
+