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 2A065200B95 for ; Tue, 13 Sep 2016 04:47:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 28A7D160AC8; Tue, 13 Sep 2016 02:47:45 +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 9409F160AB8 for ; Tue, 13 Sep 2016 04:47:44 +0200 (CEST) Received: (qmail 35456 invoked by uid 500); 13 Sep 2016 02:47:39 -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 35366 invoked by uid 99); 13 Sep 2016 02:47:39 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Sep 2016 02:47:39 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 7A1E1C09ED for ; Tue, 13 Sep 2016 02:47:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id oVI2J6jUNS69 for ; Tue, 13 Sep 2016 02:47:37 +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 DA7F35FABF for ; Tue, 13 Sep 2016 02:47:36 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id B82853102B4D for ; Mon, 12 Sep 2016 19:45:12 -0700 (PDT) Date: Mon, 12 Sep 2016 19:47:29 -0700 (PDT) From: vkulichenko To: user@ignite.apache.org Message-ID: <1473734849264-7685.post@n6.nabble.com> In-Reply-To: <1473673219869-7671.post@n6.nabble.com> References: <1473673219869-7671.post@n6.nabble.com> Subject: Re: Ignite cluster upgrades with zero downtime. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 13 Sep 2016 02:47:45 -0000 akaptsan wrote > Is there any limitations? E.g. would it be possible to perform rolling > upgrade from version 1.7 to 2.0? Hi, Major releases are generally backward incompatible, even in compile time. This most likely will be true for Ignite 2.0, so even having rolling upgrade functionality will not help in this case. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-cluster-upgrades-with-zero-downtime-tp748p7685.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.