> Eviction policy specifies the principle on which values will be evicted from > cache to free up some space in RAM. On the other hand, persistence writes the > oldest pages to the disk when RAM usage comes to a limit, so no values are > removed from the cache.
I would emphasize that the data is written to disk *all the time* (appending to the WAL, checkpointing of dirty pages from RAM) and not when you run out of RAM space. — Denis > On Aug 16, 2017, at 1:47 AM, Denis Mekhanikov <[email protected]> wrote: > > But you wrote in the previous letter that you are trying to enable eviction > policy and the node fails on such configuration. > > Eviction policy and persistence cannot be enabled at the same time, because > they solve the problem of memory lack in different ways. Eviction policy > specifies the principle on which values will be evicted from cache to free up > some space in RAM. On the other hand, persistence writes the oldest pages to > the disk when RAM usage comes to a limit, so no values are removed from the > cache. > > So, you should decide either to use persistence or eviction policy, but not > both of them. > > ср, 16 авг. 2017 г. в 11:32, Bob Li <[email protected] > <mailto:[email protected]>>: > Thank you for your response. > > Basically, I just enabled persistence configuration without any eviction > policy. > > <property name="persistentStoreConfiguration"> > <bean > class="org.apache.ignite.configuration.PersistentStoreConfiguration"> > </bean> > </property> > > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite2-1-Page-eviction-is-not-compatible-with-persistence-when-startup-tp16215p16219.html > > <http://apache-ignite-users.70518.x6.nabble.com/Ignite2-1-Page-eviction-is-not-compatible-with-persistence-when-startup-tp16215p16219.html> > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
