From notifications-return-4188-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Jul 10 12:32:12 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1AB47180675 for ; Wed, 10 Jul 2019 14:32:12 +0200 (CEST) Received: (qmail 59234 invoked by uid 500); 10 Jul 2019 12:32:11 -0000 Mailing-List: contact notifications-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list notifications@ignite.apache.org Received: (qmail 59216 invoked by uid 99); 10 Jul 2019 12:32:11 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2019 12:32:11 +0000 From: GitBox To: notifications@ignite.apache.org Subject: [GitHub] [ignite] sk0x50 commented on a change in pull request #5656: IGNITE-10663 Read Repair Message-ID: <156276193150.29090.8087533223491764113.gitbox@gitbox.apache.org> Date: Wed, 10 Jul 2019 12:32:11 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit sk0x50 commented on a change in pull request #5656: IGNITE-10663 Read Repair URL: https://github.com/apache/ignite/pull/5656#discussion_r302017574 ########## File path: modules/core/src/main/java/org/apache/ignite/IgniteCache.java ########## @@ -136,6 +136,41 @@ */ public IgniteCache withPartitionRecover(); + /** + * Gets an instance of {@code IgniteCache} that will perform backup nodes check on each get attempt. + *

+ * 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: + *

    + *
  • for transactional caches: + *

    values across the topology will be replaced by latest versioned value: + *

      + *
    • automaticaly for OPTIMISTIC || READ_COMMITTED transactions
      • + *
    • at commit() for PESSIMISTIC && !READ_COMMITTED transactions
      • + *
    + *

    consistency violation event will be recorded in case it's configured as recordable

    • + *
  • for atomic caches: consistency violation exception will be thrown.
    • Review comment: Does it make sense to record the event in that case too? ---------------------------------------------------------------- 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