Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E634619173 for ; Tue, 19 Apr 2016 21:10:19 +0000 (UTC) Received: (qmail 21273 invoked by uid 500); 19 Apr 2016 21:10:19 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 21218 invoked by uid 500); 19 Apr 2016 21:10:19 -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 21208 invoked by uid 99); 19 Apr 2016 21:10:19 -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; Tue, 19 Apr 2016 21:10:19 +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 58C491A01A9 for ; Tue, 19 Apr 2016 21:10:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 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] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id eYIFIfcty4CA for ; Tue, 19 Apr 2016 21:10:17 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id CC3785F1F3 for ; Tue, 19 Apr 2016 21:10:16 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 6A8B125A4A0A for ; Tue, 19 Apr 2016 13:56:49 -0700 (PDT) Date: Tue, 19 Apr 2016 13:56:14 -0700 (PDT) From: vkulichenko To: user@ignite.apache.org Message-ID: <1461099374583-4342.post@n6.nabble.com> In-Reply-To: References: <1460946340984-4265.post@n6.nabble.com> <57153d9d.4b93190a.31068.6eba@mx.google.com> Subject: RE: Data lost when using write-behind MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Shaomin, The EVT_NODE_FAILED is fired when any node fails and leaves topology, but you still don't know which entries are lost because you lost the write-behind queue that was on that node. Currently the only way to fully guarantee consistency between cache and DB is using write-through. After [1] is fixed, this will be also possible with write-behind in ATOMIC caches. But in TRANSACTIONAL caches write-behind store makes all DB updates separately, losing the transactional semantics on DB level, so inconsistencies will still be possible. [1] https://issues.apache.org/jira/browse/IGNITE-1897 -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-lost-when-using-write-behind-tp4265p4342.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.