Hello! I think that web session clustering will automatically remove expired sessions from cache, and you should manage session alive time via your servlet container.
Regards, -- Ilya Kasnacheev ср, 27 мая 2020 г. в 10:21, kay <[email protected]>: > Hello, I read Websession clustering page here. > > https://apacheignite-mix.readme.io/docs/web-session-clustering > > and I found this cache config for Eviction Policy. > > <bean class="org.apache.ignite.configuration.CacheConfiguration"> > > <property name="name" value="session-cache"/> > > > <property name="evictionPolicy"> > <bean > class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy"> > <property name="maxSize" value="10000"/> > </bean> > </property> > ... > </bean> > > > But I confusted because I understood cache Eviction policy for only on-heap > area. > Is it right? If I wanna config cache for session limit, I should use > on-heap > area? > > Thank you so much, I'll wait for reply. > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
