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 086C5188E2 for ; Wed, 29 Jul 2015 13:15:30 +0000 (UTC) Received: (qmail 43973 invoked by uid 500); 29 Jul 2015 13:15:29 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 43927 invoked by uid 500); 29 Jul 2015 13:15:29 -0000 Mailing-List: contact user-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.incubator.apache.org Delivered-To: mailing list user@ignite.incubator.apache.org Received: (qmail 43917 invoked by uid 99); 29 Jul 2015 13:15:29 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2015 13:15:29 +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 5FC00D88EE for ; Wed, 29 Jul 2015 13:15:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id XsFgr8NKS3O8 for ; Wed, 29 Jul 2015 13:15:26 +0000 (UTC) Received: from webmail.vfmii.com (162-253-137-22.dedicated.allstream.net [162.253.137.22]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 56154210DD for ; Wed, 29 Jul 2015 13:15:26 +0000 (UTC) Received: from VFMSRV24.visualfrenzy.com ([::1]) by VFMSRV24.visualfrenzy.com ([::1]) with mapi id 14.03.0224.002; Wed, 29 Jul 2015 09:15:32 -0400 From: Dave Ellery To: "user@ignite.incubator.apache.org" Subject: Ignite cluster upgrades with zero downtime. Thread-Topic: Ignite cluster upgrades with zero downtime. Thread-Index: AdDKAKVaZ4S77weWRNeDS3GuEA4BSw== Date: Wed, 29 Jul 2015 13:15:31 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [162.253.137.18] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 We are about to embark on using Ignite for our in-memory processing at my c= urrent place of work, now the question of how to handle upgrades has come u= p, so the main issue we are stuck on is once we have a full production depl= oyment, how will we upgrade the grid without taking it offline? Will ignite= handle this seamlessly, or will we need to come up with another strategy? I guess a basic example to fully highlight what we desire to do, say we hav= e N nodes deployed with version X, we desire to upgrade all N nodes to vers= ion Y without having to take down all N nodes. Cheers, Dave