From user-return-17443-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Jan 24 17:49:57 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 7B038180630 for ; Wed, 24 Jan 2018 17:49:57 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6BADE160C3C; Wed, 24 Jan 2018 16:49: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 B243A160C2E for ; Wed, 24 Jan 2018 17:49:56 +0100 (CET) Received: (qmail 1329 invoked by uid 500); 24 Jan 2018 16:49: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 1319 invoked by uid 99); 24 Jan 2018 16:49:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jan 2018 16:49:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 29379180701 for ; Wed, 24 Jan 2018 16:49:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.172 X-Spam-Level: ** X-Spam-Status: No, score=2.172 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] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id OFOMTbH4ae_l for ; Wed, 24 Jan 2018 16:49:52 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id E98CC5FB29 for ; Wed, 24 Jan 2018 16:49:51 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id D00D742E743D for ; Wed, 24 Jan 2018 09:49:49 -0700 (MST) Date: Wed, 24 Jan 2018 09:49:49 -0700 (MST) From: Humphrey To: user@ignite.apache.org Message-ID: <1516812589850-0.post@n6.nabble.com> Subject: Native persistence MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, I'm trying something out in minikube/minishift with native persistence and scaling. I created persistent volume and a persistence volume claim and have the IGNITE_HOME variable pointed to it. They are bounded correctly. I can see it's making a directory ${IGNITE_HOME}/work/db with underneath a folder corresponding to the node. Let's say the directory it makes is called - When I shutdown and restart I see that it claims the same volume and my data is restored. I also see it doesn't create new directory so it's using the same one (replica1). When I then scale up to 4 replica's I see that 3 other directories are created for each new node: Then I scale back down to 2 replica's. What will happen if at a later point I want to scale back up to 4 replica's? Ignite doesn't make new directories, but reuses the existing ones. - So what will happen with the data it finds in the existing directory (and probably are old), how does it handle this? - What happens in the situation that I shutdown my cluster and restart it with 2 replica's. How does ignite know which two of the four directories to re-use? Humphrey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/