You can't have on the client node "far" and "near" cache simultaneously. The error message you get on the attempt is pretty self-explanatory. So I see not bug here.
2016-05-05 17:13 GMT+03:00 zshamrock <aliaksandr.kaz...@gmail.com>: > 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. > -- Best regards, Alexei Scherbakov
