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 5EB702009E8 for ; Mon, 30 May 2016 16:28:20 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5D195160A3C; Mon, 30 May 2016 14:28:20 +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 7B9FC160969 for ; Mon, 30 May 2016 16:28:19 +0200 (CEST) Received: (qmail 71504 invoked by uid 500); 30 May 2016 14:28:18 -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 71494 invoked by uid 99); 30 May 2016 14:28:18 -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; Mon, 30 May 2016 14:28:18 +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 2D9921804C2 for ; Mon, 30 May 2016 14:28:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.398 X-Spam-Level: ** X-Spam-Status: No, score=2.398 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, KAM_LINEPADDING=1.2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 lhRwQzW-yeYo for ; Mon, 30 May 2016 14:28:17 +0000 (UTC) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 91CFE5F1F3 for ; Mon, 30 May 2016 14:28:16 +0000 (UTC) Received: by mail-qg0-f52.google.com with SMTP id q32so78762629qgq.3 for ; Mon, 30 May 2016 07:28:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=atKloQd2QjF3ff1OqSSngwf7OBew4zm85LpPnhu7z+I=; b=c3ejDBtxfbmmQOwBnRmjKL8sGW4SwMcriOjAx2KGwcaQ1WR8CPDR4KHK4H+GFpiLAJ hqEibiQTXQQ61CVxYck6Ta/bEfpBgUEWlbPjJemzZ0kFeqAT/oRSC6UiUuRI20kNlBW/ 6SFCKZoWQgUItaGiGD21TvMpiDI9DmxaYHyCMmBqEgvSuiUQBtp1yjnO940SdFPRL0dP Liol+5PWpda5pn3HNAf87n3HrkkNVQPfW8MWScqnU5YnI25oqLROWZOCm1tOQD3NpsPJ VlzxvUZZ3+oNpWjzFMTpBMk17k79VCmHeR+iTNCFItSzGvaaJfrOboid//uxcxA8842X mwzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=atKloQd2QjF3ff1OqSSngwf7OBew4zm85LpPnhu7z+I=; b=jnQ1WQcqoMVWjw+CSkhQ6rJHHl5lr1v9/Ummu9JB0CuhBOj65R+J1rnIe4U3YRrZwq 2mGQ+fSUfmQmviCAuZh2vvwOq/8+i9o+VArs+ZKwXGNK2YU+e0HKAnKffss8s17w5cp8 fYZxgB8vDGzsUzEkcrq9DHeA414XpWW/q3mdUDFwZWYrjP7Fu1XnP6++iB2UUyUfVMKt MmUGnSpdm8wn3omV47vRQPEphvZHjV/UbCTYVxcYiwWY64cmvhB7g91+xqtvScsKLSm5 2dkpGJeMS7SejOAVYuBNpLufF6IrZYZmPdHTUETLbKx7V1XuHAORN3zVOZiLkjewpNCT hX6g== X-Gm-Message-State: ALyK8tLu0XLzoYsxR6qO5RolOUerQmlbslAQfwqKek+AtDNzjL3hzYV6E7wBu/vSuZo+sVv8XSABbIl1jlwWeg== MIME-Version: 1.0 X-Received: by 10.140.203.208 with SMTP id y199mr1483342qha.45.1464618495627; Mon, 30 May 2016 07:28:15 -0700 (PDT) Received: by 10.140.89.7 with HTTP; Mon, 30 May 2016 07:28:15 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 May 2016 17:28:15 +0300 Message-ID: Subject: Re: How to update Ignite config in Production Environment From: Alexei Scherbakov To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=001a114f55cc29dbff0534101119 archived-at: Mon, 30 May 2016 14:28:20 -0000 --001a114f55cc29dbff0534101119 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, 1. You can destroy cache (IgniteCache.destroy) and recreate it dynamically with new configuration. Data must be backed up somethere(on example in the other cache) until the process is finished. Don't forget to update Ignite's startup configurations on all server nodes or you will lose changes on restart. 2. Ignite validates cluster configuration on the node join. If configuration of the node is not compatible with the current it not will not be allowed to join topology. 2016-05-30 15:45 GMT+03:00 =E5=BC=A0=E9=B9=8F=E9=B9=8F : > Hi,I have some questions about using Ignite in the production > environment. > > 1=E3=80=81I have 3 Ignite nodes as Server,My Java application uses Ignite= as > client. > Now,I just use Ignite as JCache implements. > > When I want to update the Cache config,like adding indexs,What's the > best way to do it? > > I don't want to lost data in the server,So,I replace server@1's > config,then restart it.I must wait data rebalancing finish.Then I do the > same to the server@2 and so on! > > I want to do it automatic.But How can I get the rebalancing finishin= g > event in Linux console? > And Is it the only way to update the config If I don't want to lose the > cache data? > > > > 2=E3=80=81If the server config is different,which one is valid?Is it the = last > started one? > > Today,I restarted Ignite server by mistake.I used old config to > restart one node in the Clusters. > The scenes is: > server@1 -- old config --restart > server@2 -- old config > server@3 -- new config > > server@1 and server@2 are using old config,server@3 is using new > config. > I restart server@1 by mistake. > > > Then My application appeard > "Cannot find metadata for object with compact footer: 1236746791" > exception. > > The server occured exceptions too,and the cache couldn't use anymore. > > Finally,I killed all the application used Ignite client,then update all > the Ignite config and restart all the Ignite Server. > > > I don't know why I must kill all the Ignite client so I can restart the > Ignite server correctly. > > > > > > > > > --=20 Best regards, Alexei Scherbakov --001a114f55cc29dbff0534101119 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

1. You can destroy cache (IgniteCac= he.destroy) and recreate it dynamically with new configuration.
D= ata must be backed up somethere(on example in the other cache) until the pr= ocess is finished.
Don't forget to update Ignite's startu= p configurations on all server nodes or you will lose changes on restart.

2. Ignite validates cluster configuration on the no= de join. If configuration of the node is not compatible with the current
it not will not be allowed to join topology.

2016-05-30 15:45 GMT+03:00 =E5=BC= =A0=E9=B9=8F=E9=B9=8F <zhangpp520@gmail.com>:
=C2=A0Hi,I have some questions= about using=C2=A0Ignite=C2=A0in the =C2=A0production environment.

1=E3=80=81I have 3 Ignite nodes as Server,My Java applicat= ion uses Ignite as client.
=C2=A0 =C2=A0 =C2=A0Now,I just use Ign= ite as JCache implements.

=C2=A0 =C2=A0 =C2=A0When= I want to update the Cache config,like adding indexs,What's the best w= ay to do it?

=C2=A0 =C2=A0 =C2=A0I don't want = to lost data in the server,So,I replace server@1's config,then restart = it.I must wait data rebalancing finish.Then I do the same to the server@2 a= nd so on!

=C2=A0 =C2=A0 =C2=A0I want to do it=C2= =A0automatic.But How can I get the=C2=A0rebalancing=C2=A0finishing event in= Linux console?
And Is it the only way to update the config If I = don't want to lose the cache data?


<= div>
2=E3=80=81If the server config is different,which one is= =C2=A0valid?Is it the last started one?

=C2=A0 =C2= =A0 =C2=A0Today,I restarted Ignite server by mistake.I used old config to r= estart one node in the Clusters.
=C2=A0 =C2=A0 The=C2=A0scenes is= :
=C2=A0 =C2=A0 server@1 =C2=A0-- old config =C2=A0--restart
=C2=A0 =C2=A0 server@2 =C2=A0-- old config
=C2=A0 =C2=A0 se= rver@3 =C2=A0-- new config

=C2=A0 =C2=A0 serv= er@1 and server@2 are using old config,server@3 is using new config.
<= /div>
=C2=A0 I restart server@1 by mistake.

=C2=A0Then My application=C2=A0appeard=C2=A0
"C= annot=C2=A0find=C2=A0metadata=C2=A0for=C2=A0object=C2=A0with=C2=A0compact= =C2=A0footer:=C2=A01236746791" =C2=A0exception.

=C2=A0The server=C2=A0occured exceptions too,and the cache couldn't = use anymore.

=C2=A0Finally,I killed all the applic= ation used Ignite client,then update all the=C2=A0Ignite=C2=A0config =C2=A0= and restart all the Ignite Server.


= I don't know why I must kill all the Ignite client so I can restart the= Ignite server =C2=A0correctly.









--

Best r= egards,
Alexei Scherbakov
--001a114f55cc29dbff0534101119--