There are several options how you can deal with this: 1) define caches in Spring XML configuration of all server nodes and start near caches on clients when needed; 2) start a special client that will initialize all required caches dynamically and stop it after that. The rest of the clients can later create near caches for the caches created by that client.
— Denis > On May 5, 2016, at 5:13 PM, zshamrock <aliaksandr.kaz...@gmail.com> wrote: > > Yes, removing definition of the cache from IgniteConfiguration, helps. And I > know about this. > > The point was that I wanted for the client to be self sufficient, i.e. to > create all the distributed server caches first (by providing cache > definition for IgniteConfiguration), and then configure the near cache. > > Although, I've switched from this direction, and only configure now near > cache for the client. But, still the scenario described could be a valid > one. And it is for you to evaluate whether this is the expected behavior or > a bug. > > Thank you. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-near-cache-conflicts-with-server-distributed-cache-tp4768p4792.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
