From dev-return-30930-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Tue Feb 13 07:36:31 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id A522E180656 for ; Tue, 13 Feb 2018 07:36:31 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 94E81160C53; Tue, 13 Feb 2018 06:36:31 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D978C160C50 for ; Tue, 13 Feb 2018 07:36:30 +0100 (CET) Received: (qmail 40321 invoked by uid 500); 13 Feb 2018 06:36:29 -0000 Mailing-List: contact dev-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 dev@ignite.apache.org Received: (qmail 39458 invoked by uid 99); 13 Feb 2018 06:36:28 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Feb 2018 06:36:28 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E5BF5180145; Tue, 13 Feb 2018 06:36:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.129 X-Spam-Level: ** X-Spam-Status: No, score=2.129 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id WaZLMl0Uzfil; Tue, 13 Feb 2018 06:36:26 +0000 (UTC) Received: from mail-ot0-f177.google.com (mail-ot0-f177.google.com [74.125.82.177]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 285285F21E; Tue, 13 Feb 2018 06:36:26 +0000 (UTC) Received: by mail-ot0-f177.google.com with SMTP id r23so16311549ote.8; Mon, 12 Feb 2018 22:36:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=9CZX3Ue+nrMvaQohNAIkBGngWM/p1XlAONI6Xxf8rBc=; b=XFNTXqQFR9QaZQW0CYrYRNdnAIhuXvg/PGWoxXs+1EQjM+4kFc/CHPn9gVRmhXlNoz wwAPPiRX39YvtCOGxIHwenMdHlCWGE5zLdberN7In1DxZ/o5iDx89jbr/ELs+SLx7i8h 5MPFzCl3TC721fYqmMLE2eZ935/2PTJGFrjMOhlj7aUJ8jwiPABYIdG7cgBwT5OD/LZh MWwy8/DTW7aA+Sep9fDVfx4M3WYASBQ7TGvrYNFIubaYGPIe9zkKKO4pFoqDSo/QxbcH MyR4cPz5kJpHQggtiakMlg1HBlraSA7A6LIJh3m+6/0SckUG9jCkCyzCfdlHdkJN9c3O bktg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=9CZX3Ue+nrMvaQohNAIkBGngWM/p1XlAONI6Xxf8rBc=; b=dsYKdZ0OnNsRhZOuBDRCS6aa1xa1Q/shfbcIk1DlQpAp7UFJhZBfz/3xr2sWYM/Vje jrp2/rUE949pFFNlMgCTJzu5EmGfEutdW1KxAre9bBs5f8Zy+vUQPYe/96Zca6S/lzbF /rRzj/l0wjnwp4xhl9Q9j9mgU8fNff9PN4o8ambevHGVtnEe5vuBGIW8qE/1O+jX0pul I5J/cMXYMimBKDVRI8Lh3PD0a5rPx7xpUKOIakEmbNIAwRNF/7yZZ5SyD57QLlL0oFCX HrLnuuSeYZI/l8njSAV+3URLMYmpzFMsKpXO7fYRisN/PhUcNuizNXeIrB7TwmcoLbjf L0XQ== X-Gm-Message-State: APf1xPBeOGJLB56BJbgSwvi1+Y7TbiX3lj9a9pEwFoMzj74G9MgUkWG8 hNYdb/OhKY/vrWotEub9SfmyR7B+Lmnw1lGUOaaW8w== X-Google-Smtp-Source: AH8x2264zsTTaaaHAtf9I6FrdaZx2blAe0q6wA35rlFmxGmLgCeVCWTEkmpzXDXQLPTLSlL3hb8uqAZDjqUlUOLqcn8= X-Received: by 10.157.52.52 with SMTP id v49mr155258otb.12.1518503785329; Mon, 12 Feb 2018 22:36:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.23.230 with HTTP; Mon, 12 Feb 2018 22:36:24 -0800 (PST) In-Reply-To: References: <1518492803250-0.post@n6.nabble.com> From: John Wilson Date: Mon, 12 Feb 2018 22:36:24 -0800 Message-ID: Subject: Re: What happens if Primary Node fails during the Commit Phase To: user@ignite.apache.org, dev@ignite.apache.org Content-Type: multipart/alternative; boundary="001a1140c790b6f9a605651236c4" --001a1140c790b6f9a605651236c4 Content-Type: text/plain; charset="UTF-8" I got the answer for #3 here https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood#IgniteDurableMemory-underthehood-Pages&links. I will post the remaining questions in a separate thread. On Mon, Feb 12, 2018 at 8:03 PM, John Wilson wrote: > You're always helpful Val. Thanks! > > > I have a question regarding Optimistic Locking > > > 1. The documentation here, https://cwiki.apache. > org/confluence/display/IGNITE/Ignite+Key-Value+Transactions+ > Architecture > , > states that locks, for optimistic locking, are acquired during the > "prepare" phase. But the graphic depicted there and the tutorial here, > https://www.gridgain.com/resources/blog/apache-ignite-transactions- > architecture-concurrency-modes-and-isolation-levels > , > clearly indicate that locks are acquired during the commit phase; with a > version information passed along with the key by the coordinator to the > primary nodes. Can you please explain the discrepancy? > > And two questions regarding pages and page locking? > > 1. Does Ignite use a lock-free algorithm for its B+ tree structure? > Looking at the source code and the use of a tag field to avoid the ABA > problem suggests that. > 2. Ignite documentation talks about entry-level locks and page locks. > When exactly is a page locked and released? Also, when an entry is > inserted/modified in a page, is the page locked, forbidding other threads > from inserting other entries in the page, or only the entry's offset is > locked allowing other threads to insert other entries in the page? > 3. What is the the difference between a directCount and indirectCount > for a page? > > Thanks > > On Mon, Feb 12, 2018 at 7:33 PM, vkulichenko < > valentin.kulichenko@gmail.com> wrote: > >> Hi John, >> >> 1. True. >> >> 2. The blog actually provides the answer: >> >> When the Backup Nodes detect the failure, they will notify the Transaction >> coordinator that they committed the transaction successfully. In this >> scenario, there is no data loss because the data are backed up and can >> still >> be accessed and used by applications. >> >> In other words, if primary node fails, backups will not wait for a >> message, >> but instead will commit right away and send an ack to the coordinator. >> Once >> coordinator gets all required acs, transaction completes. >> >> -Val >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> > > --001a1140c790b6f9a605651236c4--