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 2736D200B81 for ; Tue, 13 Sep 2016 21:00:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 25C26160AD2; Tue, 13 Sep 2016 19:00:15 +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 92BE0160AAA for ; Tue, 13 Sep 2016 21:00:14 +0200 (CEST) Received: (qmail 60523 invoked by uid 500); 13 Sep 2016 19:00:13 -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 60513 invoked by uid 99); 13 Sep 2016 19:00:13 -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 Sep 2016 19:00:13 +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 49A6DC6784 for ; Tue, 13 Sep 2016 19:00:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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-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 RgHV5kqM49k3 for ; Tue, 13 Sep 2016 19:00:11 +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 EE9C85FB2E for ; Tue, 13 Sep 2016 19:00:10 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 43DD131103A0 for ; Tue, 13 Sep 2016 11:57:49 -0700 (PDT) Date: Tue, 13 Sep 2016 12:00:10 -0700 (PDT) From: vkulichenko To: user@ignite.apache.org Message-ID: <1473793210615-7721.post@n6.nabble.com> In-Reply-To: References: <8DBE852B3B58DF4EB5BF74BB95BD881D2FF13E36@actinium.iisy.lan> Subject: Re: Write Behind data safety guarantees II MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 13 Sep 2016 19:00:15 -0000 Hi, In current implementation write-behind store can lose writes even if only one nodes fails. This can be improved by adding backup queues [1], but it's not implemented yet. Of course, this will not help if you lose more nodes than number of backups you have (in this case data in memory is also lost). Only synchronous write-through can guarantee that there are no data loss. [1] https://issues.apache.org/jira/browse/IGNITE-1897 -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Write-Behind-data-safety-guarantees-II-tp7696p7721.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.