Markus, Try LruEvictionPolicy.
Great to hear that Ignite makes migration from Hazelcast easy :) D. On Wed, Apr 8, 2015 at 8:18 PM, Markus Wiesenbacher < [email protected]> wrote: > Thanks Dmitriy, > > another question please: My tests fail because of missing > CacheLruEvictionPolicy, ist there any replacement? > > BTW: Great product, I´ve changed my Hazelcast-based application to > GridGain/Ignite within hours. Thumbs up! > > Many thanks > Markus > > -----Ursprüngliche Nachricht----- > Von: Dmitriy Setrakyan [mailto:[email protected]] > Gesendet: Donnerstag, 9. April 2015 00:46 > An: [email protected] > Cc: [email protected] > Betreff: Re: CacheDistributionMode > > Hi Markus, > > First of all, thanks for your interest in Apache Ignite. > > There is no need for CacheDistributionMode at all anymore. You can > configure PARTITIONED, or REPLICATED cacheMode and the cache will be > automatically deployed on all the data nodes. > > If you need to connect to it from a client, simply call > "Ignite.getOrCreateCache(...)" method from the client side and you will get > client side access to it. > > If you need to configure a Near cache on the client side, then you should > call "Ignite.getOrCreateNearCache(...)" method. > > More information can be found here: > - Deploying clients and servers: > http://apacheignite.readme.io/v1.0/docs/clients-vs-servers > > - Near Caches: > http://apacheignite.readme.io/v1.0/docs/near-caches > > Let us know if you have more questions. > > Thanks, > D. > > On Wed, Apr 8, 2015 at 1:41 PM, Markus Wiesenbacher < > [email protected]> > wrote: > > > Hi guys, > > > > > > > > what is the replacement for the class CacheDistributionMode in v1.0.0? > > > > > > > > Thanks > > > > Markus ;) > > > > > >
