Shiva, Just to clarify, the peer class loading (p2p) is a global setting and can be set to on/off for particular nodes.
As for your case, the client has to send a compute tasks or execute p2p-enabled API first and after that a server which will be processing the task/request will preloading missing classes. Do you use p2p this way? - Denis On Wed, Jan 23, 2019 at 10:15 AM shivakumar <[email protected]> wrote: > hi stan, > thanks for your reply!! > > but in my case, i deployed ignite in kubernetes environment and starting a > client node on VM, which connects to ignite server(client is configured to > use org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder > as discovery mechanism and provided IP address of ignite server > pods/containers ) > and i am placing "keytype" and "valuetype"(custom key and values) class > files in clientnode's class path (under libs folder of apache ignite HOME > path where i start client process) but servers are not loading these > classes > and throwing class not found exception for those classes and if i place > those classes inside pods its loading the classes. > why it is not loading the class files when i placed on client side even > when > peerClassLoading is enabled on client side? > am I missing something? > > with thanks, > shiva > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
