By the way, there are SortedEvictionPolicy and new parameters like batchSize and maxMemorySize and are not documented on readme.io yet. See javadoc of corresponding classes for details.
On Thu, Aug 6, 2015 at 8:17 AM, Dmitriy Setrakyan <[email protected]> wrote: > > On Wed, Aug 5, 2015 at 10:03 PM, kcheng.mvp <[email protected]> wrote: > >> Might be a good idea to support multiple eviction policy, i have used >> Hazelcast in a project. it support multiple eviction policy. >> > > I don't think support for multiple eviction policies for a single cache > makes sense. I would be very surprised if Hazelcast supports it. > > Ignite does support multiple eviction policies for different caches. Each > cache can have its own different eviction policy. > > Moreover, unlike Hazelcast, eviction policies in Ignite are pluggable and > you can plug in your own implementation, if none of the provided ones fit. > > More on eviction policies here: > https://apacheignite.readme.io/docs/evictions > > If this behavior is not enough, can you please give an example of what > kind of behavior you are looking for? > > D. > > >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/How-to-configure-multiple-evictionPolicy-and-What-s-the-behavior-tp838p842.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > > -- Andrey Gura GridGain Systems, Inc. www.gridgain.com
