Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9835C200BC2 for ; Thu, 17 Nov 2016 21:29:57 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 96901160B0B; Thu, 17 Nov 2016 20:29:57 +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 1230E160AD8 for ; Thu, 17 Nov 2016 21:29:56 +0100 (CET) Received: (qmail 7371 invoked by uid 500); 17 Nov 2016 20:29:51 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 7361 invoked by uid 99); 17 Nov 2016 20:29:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Nov 2016 20:29:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id CFED21A06FC for ; Thu, 17 Nov 2016 20:29:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.174 X-Spam-Level: ** X-Spam-Status: No, score=2.174 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id UVTUGFgRDrbq for ; Thu, 17 Nov 2016 20:29:48 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A414C5FC4A for ; Thu, 17 Nov 2016 20:29:48 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id D2DAF3633B2B for ; Thu, 17 Nov 2016 12:19:33 -0800 (PST) Date: Thu, 17 Nov 2016 13:29:40 -0700 (MST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1479414580605-9058.post@n6.nabble.com> In-Reply-To: <1479373191897-9036.post@n6.nabble.com> References: <1477650926041-8586.post@n6.nabble.com> <1477680788078-8593.post@n6.nabble.com> <1478505281454-8726.post@n6.nabble.com> <1478644649587-8801.post@n6.nabble.com> <1479373191897-9036.post@n6.nabble.com> Subject: Re: Explicit lock whithin a transaction MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Thu, 17 Nov 2016 20:29:57 -0000 So what is read-only in this example? You're updating the account balance after you read it - this is a classic use case for REPEATABLE_READ. If there is something else that you read, but don't update, I would just do this outside of transaction. Makes sense? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p9058.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.