From dev-return-30928-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Tue Feb 13 05:03:46 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 35D9D180652 for ; Tue, 13 Feb 2018 05:03:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 25EFA160C61; Tue, 13 Feb 2018 04:03:46 +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 6BCC0160C3F for ; Tue, 13 Feb 2018 05:03:45 +0100 (CET) Received: (qmail 94012 invoked by uid 500); 13 Feb 2018 04:03:39 -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 93566 invoked by uid 99); 13 Feb 2018 04:03:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Feb 2018 04:03:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id EB30CC1A12; Tue, 13 Feb 2018 04:03:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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: spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id m20vrSlJoadp; Tue, 13 Feb 2018 04:03:35 +0000 (UTC) Received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com [209.85.218.53]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 6D36D5F21E; Tue, 13 Feb 2018 04:03:35 +0000 (UTC) Received: by mail-oi0-f53.google.com with SMTP id l124so661418oib.0; Mon, 12 Feb 2018 20:03:35 -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=G4/60MRKEggRjUQ47VpKm7u4B4P/3mniw9E6eZ7fsMg=; b=mHIBeMs5opWXmqZVi7llnW5sR5FdDBjbjgFw0GzDtOBSqj4SaVK7cxYQcQ/KWV33zC H0l0w2sP3KnwCpRQpnX0F2nce3kreG60FknyDzcYEV8ohJUbjPjnm/ilVQW4xR2qLI3X 8GH9ixZuXbvzA0UnsO5akt9mfB663s9MmuJPWDhwMO4LquumYuf0qVeqKVAa3AgAwdjb yjCnMIdBtnrWc4gEatbcquvFja8Feeh0nTV6O67ehn63y5VzMb+JluYE9pYOicY5bF2V AZDycMUU+K+Alit/a+f4jWr9mMANzC9Fqhm8MlSqym02QYh+9Qpdb/r1F3jsud050JxD zypQ== 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=G4/60MRKEggRjUQ47VpKm7u4B4P/3mniw9E6eZ7fsMg=; b=WYiJ8TJy8+cPtmbew1cOFwTg8sNT4klz44NISwJDtcNH6ACZUT99G/HWzcEXWE6DuW VPeRiuz+CDvl32Nxf/poRgK62vboXcAYWLBVuOzEby+IR9crE84LebSl0rq+TNpulQyO +bB+Izr+7FjrWExKwuwZFoRFR9DL4yA7VquGubqiSSLB1k2CfzevgXSQagYbZdSS516h VZDu7NGZTGT+lX7xQrhxgLKS9hXsY6CDbJGvDlAH97nP1EqwyWnEtO6mjnHu9HYw0Ab7 Fc5guidcLQUixKbAnVSEhf9M+EbNGbN4Q0g7B1dT9myIXl5jp+udFHfKAAkXgba20Csh h2gQ== X-Gm-Message-State: APf1xPAB2G4+EY1fjajulJNR2G0N0ltEZjLZEQ+BaZjgLibdcLX2A425 lGMwC06BVGaXPOnCq9NL5AOwYnLSLv1BGxa68iojbQ== X-Google-Smtp-Source: AH8x227wcjRVnaFVjJdVLPOqyOYaw/v4KmA64mRVXkd6JEW0uL8yAEmMxBDRhaiwxkaecOrQsK5L4/2Wrjd9eXiEgiU= X-Received: by 10.202.49.13 with SMTP id x13mr172349oix.351.1518494614542; Mon, 12 Feb 2018 20:03:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.23.230 with HTTP; Mon, 12 Feb 2018 20:03:34 -0800 (PST) In-Reply-To: <1518492803250-0.post@n6.nabble.com> References: <1518492803250-0.post@n6.nabble.com> From: John Wilson Date: Mon, 12 Feb 2018 20:03:34 -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="001a113cca3617de4d0565101407" --001a113cca3617de4d0565101407 Content-Type: text/plain; charset="UTF-8" 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 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/ > --001a113cca3617de4d0565101407--