You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ignite.apache.org by GitBox <gi...@apache.org> on 2019/07/11 05:54:37 UTC

[GitHub] [ignite] anton-vinogradov commented on a change in pull request #5656: IGNITE-10663 Read Repair

anton-vinogradov commented on a change in pull request #5656: IGNITE-10663 Read Repair
URL: https://github.com/apache/ignite/pull/5656#discussion_r302373119
 
 

 ##########
 File path: modules/core/src/main/java/org/apache/ignite/IgniteCache.java
 ##########
 @@ -136,6 +136,41 @@
      */
     public IgniteCache<K, V> withPartitionRecover();
 
+    /**
+     * Gets an instance of {@code IgniteCache} that will perform backup nodes check on each get attempt.
+     * <p>
+     * Read Repair means that each backup node will be checked to have the same entry as primary node has,
+     * and in case consistency violation found:
+     * <ul>
+     *  <li>for transactional caches:
+     *  <p>values across the topology will be replaced by latest versioned value:
+     *  <ul>
+     *      <li>automaticaly for OPTIMISTIC || READ_COMMITTED transactions</li>
+     *      <li>at commit() for PESSIMISTIC && !READ_COMMITTED transactions</li>
+     *  </ul>
+     *  <p>consistency violation event will be recorded in case it's configured as recordable</li>
+     *  <li>for atomic caches: consistency violation exception will be thrown.</li>
 
 Review comment:
   No, since it can be false positive.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services