Mailing-List: contact user-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.incubator.apache.org
Date: Wed, 27 May 2015 20:40:54 -0700 (PDT)
From: dsetrakyan <dsetrakyan@apache.org>
To: user@ignite.incubator.apache.org
Message-ID: <1432784454611-421.post@n6.nabble.com>
In-Reply-To: 
 <CAPzt5W7fM_76bgC6F2zqnsTsaCQU57rfepAZ3u=Xmbci7xCNaA@mail.gmail.com>
References: <1432737068843-416.post@n6.nabble.com>
 <CAPzt5W61o3MkEwc3Yg_V_kqJ=VtBD2GWyhPp84Tmc-MEvxFJJA@mail.gmail.com>
 <CAOsHXW2KJGcHeyz=-Wum-3e3nM6PHJOOY_Gs1j9h7UhpKG=4cg@mail.gmail.com>
 <CAPzt5W7fM_76bgC6F2zqnsTsaCQU57rfepAZ3u=Xmbci7xCNaA@mail.gmail.com>
Subject: Re: About peer class loading
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

If you enable peer class loading, you can use either SHARED or CONTINUOUS
deployment modes in cache. In either mode Ignite will automatically deploy
your classes without having to copy jars into the lib folder. 

In SHARED mode, once Ignite detects that all client nodes have left, it will
clear up all the caches. This mode is useful during the development.

In CONTINUOUS mode Ignite will not clear caches once the clients have left,
but in this case it is up to the user to ensure that class definitions don't
change throughout the life time of the cluster.

Unfortunately, both of these modes will require you to restart the cluster
if you change your data classes. The reason for that is that Ignite does not
allow to have classes from different class loaders residing in the same
cache.

D.


-----
D.
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/About-peer-class-loading-tp416p421.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.