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 3A2CB200CFA for ; Tue, 5 Sep 2017 17:28:58 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 38D89161421; Tue, 5 Sep 2017 15:28:58 +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 A6F1B160BE4 for ; Tue, 5 Sep 2017 17:28:57 +0200 (CEST) Received: (qmail 81733 invoked by uid 500); 5 Sep 2017 15:28:55 -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 81723 invoked by uid 99); 5 Sep 2017 15:28:55 -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, 05 Sep 2017 15:28:55 +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 BD23E1A1FB8 for ; Tue, 5 Sep 2017 15:28:54 +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, SPF_HELO_PASS=-0.001, 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 BDfzxXODfzjJ for ; Tue, 5 Sep 2017 15:28:50 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0B8795FD33 for ; Tue, 5 Sep 2017 15:28:50 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 7C40418844A9 for ; Tue, 5 Sep 2017 08:28:49 -0700 (MST) Date: Tue, 5 Sep 2017 08:28:49 -0700 (MST) From: userx To: user@ignite.apache.org Message-ID: <1504625329506-0.post@n6.nabble.com> In-Reply-To: References: <1504620316094-0.post@n6.nabble.com> Subject: Re: IgniteDataStreamer.addData - behavior for a FULL_SYNC Cache MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 05 Sep 2017 15:28:58 -0000 Hi Mikhail, I am just trying to understand the behavior of addData method in conjunction with FULL_SYNC. If we have just one server node left, then we are not really replicating, isn't it ? So let's say we have to persist 2 entries, and after 1 write and replication, one of the server goes down, then eventually the second write is just written to one server and replication does not come into the picture. Again, I am just trying to understand whats the responsibility of addData keeping in mind it throws exception in its declaration. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/