“Classes deployed within the same class loader on the master node still share the same class loader remotely on worker nodes. However, the tasks deployed from different master nodes does not share the same class loader on worker nodes. This is useful in development environments when different developers can be working on different versions of the same classes"
https://ignite.apache.org/docs/latest/code-deployment/peer-class-loading > On 15 Nov 2021, at 11:39, Surinder Mehra <redni...@gmail.com> wrote: > > Does this mean same ignite node can use dufferent app libs to execute > business logic. Or does a node takes lib version at startup and only process > that version through its life cycle, and it is part of same cluster > cobtaining other nodes with different app version. Could you please point me > to documentation if any. > > On Mon, Nov 15, 2021, 16:37 Stephen Darlington > <stephen.darling...@gridgain.com <mailto:stephen.darling...@gridgain.com>> > wrote: > You might need to set the deployment mode to PRIVATE/ISOLATED but otherwise > it should pretty much just work. > >> On 14 Nov 2021, at 04:37, Surinder Mehra <redni...@gmail.com >> <mailto:redni...@gmail.com>> wrote: >> >> Any suggestions from experts ? >> >> On Thu, Nov 11, 2021, 23:49 Surinder Mehra <redni...@gmail.com >> <mailto:redni...@gmail.com>> wrote: >> Hi, >> I have a special requirement to support deploying several versions of same >> class file on same ignite cluster. Say customer 1 wants some additional >> features on same file but other clients continue working with old version. >> Just trying to think if it is possible in ignite or i have to think about >> having separate ignite cluster for each version. > >
